# SYSPRO Debit Note Table: Finding AP and AR Transaction Tables

> Source: https://netray.co/erp-help/syspro-debit-note-and-ap-ar-transaction-tables
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

SYSPRO stores supplier invoices and related documents in the Accounts Payable tables and customer documents in the Accounts Receivable tables, with the SQL Server names prefixed by module such as Ap and Ar (for example ApSupplier, ApInvoice, ArCustomer). We cannot confirm one dedicated debit note table across releases, so identify yours by querying the catalog and testing with a known document.

## Kind

advanced

## System

syspro

## Erp

SYSPRO

## Module

SQL tables / Accounts Payable / Accounts Receivable

## Query

syspro debit note table

## Alternate Queries

- syspro sql table list
- syspro apinvoice table
- syspro arinvoice table
- syspro database tables ap ar

## Applies To

SYSPRO 7 and 8 on SQL Server. Table and column names can differ by release and modules, so verify them in your own database before building reports.

## Steps

### How to find the debit note data in your SYSPRO database

**Items:**

- Post a known test debit note in a test company and note the supplier, document number and date.
- Query INFORMATION_SCHEMA.TABLES for tables starting with Ap to list the Accounts Payable tables in your release.
- Query INFORMATION_SCHEMA.COLUMNS for the candidate tables and look for document type, invoice number, supplier, amount and date columns.
- Run a read-only SELECT on the candidate table filtered by your test supplier and document number, and confirm the debit note appears and how its type is flagged.
- Check sign conventions: debit notes may be stored as negative values or flagged by a document type code, which affects totals.
- Wrap the working query in a view and document it, then build reports on the view rather than on raw tables.

## Sections

### Discovering the schema

**Body:**

Never rely on a table list copied from another site, because modules, releases and customisations change the schema. Your own database is the reference, and a few catalog queries give a complete picture quickly.

Use a read-only login and, ideally, a restored copy of production. Do not point exploratory queries at the live transaction database during business hours.

**Code:**

-- List Accounts Payable tables
SELECT TABLE_NAME
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_NAME LIKE 'Ap%'
ORDER BY TABLE_NAME;

-- Columns of a candidate table
SELECT COLUMN_NAME, DATA_TYPE
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'ApInvoice'
ORDER BY ORDINAL_POSITION;

### AP and AR structure in general

**Body:**

SYSPRO separates master tables, such as the supplier and customer masters, from transaction tables holding documents, and from posted or history tables used for ageing and inquiries. Keys normally combine the supplier or customer code with the document or invoice number, and often a branch.

Debit and credit notes in AP and AR are documents like invoices, flagged by type. Always test totals against a SYSPRO inquiry or report so you know your query handles sign and type the same way.

### Safe reporting practice

**Body:**

Build views in a separate schema, grant report users access to the views only, and never write to SYSPRO tables with SQL. Updates must go through SYSPRO or the e.net business objects so that journals, balances and audit data stay consistent.

When an upgrade changes the schema, only the view definition needs maintenance, and the downstream reports continue to work.

## Pitfalls

- Assuming a table name from a forum without checking your database.
- Summing document amounts without handling debit and credit note sign or type.
- Writing to SYSPRO tables directly, which breaks reconciliation.
- Running heavy queries on the live database during peak hours.
- Skipping a reconciliation of the query result to a SYSPRO report.

## Ai Angle

Netray adds a private AI layer to the SYSPRO you already run, including on-prem installs where the SQL Server and application server never leave your network. ERPray answers questions over live SYSPRO data with read-only SQL or e.net queries it shows you, under the operator's own SYSPRO security, so a planner or accountant can ask the question in plain language and see exactly which tables or business objects produced the answer. Any write-back, such as posting a transaction, goes through a human approval step. The model is open-weight and runs on your own GPUs, so company data is not sent to a public AI service.

## Faq

### What table stores debit notes in SYSPRO?

**Answer:** AP debit notes are held with Accounts Payable documents, but the exact table and type flag should be confirmed in your own database. Post a test debit note, then search the Ap tables for it, and verify against a SYSPRO report.

### Are SYSPRO table names consistent?

**Answer:** They follow a module prefix convention such as Ap for payables and Ar for receivables, but details vary by release and installed modules. Use the catalog views on your own database as the source of truth.

### Can I update SYSPRO tables with SQL?

**Answer:** No. Direct updates bypass journals and validation and cause reconciliation problems. Use SYSPRO functions or the e.net business objects for any change, and keep SQL access read-only.

### How do I get AP aged balances from SQL?

**Answer:** Query the AP document tables and apply the same ageing logic as the SYSPRO report, then reconcile your totals to that report. Document types and signs matter, so test with known suppliers.

## Search terms

syspro debit note table, syspro sql tables, syspro apinvoice, syspro arinvoice, syspro database schema, syspro ap tables, syspro ar tables, table sispro

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json