Account Receivable (Debtor)
A debtor is a customer who owes a company money for goods delivered or services rendered. In accounting, the debtor is also the personal customer account on which this open receivable is kept.
A debtor is a company’s debtor – specifically a customer who still owes payment for goods delivered or a service rendered. The term has two closely related meanings: colloquially it refers to the person or company that owes something, while in accounting it means the personal customer account on which the receivables from goods and services against exactly this customer are recorded.
Debtors always arise when a sale is made on account with a payment term rather than against immediate payment. The sum of all debtor accounts forms the trade receivables and thus a central item of current assets on the balance sheet. These accounts are managed, monitored and settled in accounts receivable, a subledger of financial accounting.
At a glance
- Debtor = customer with an open receivable; also the associated accounting account
- Arises with a sale on account with a payment term
- Sum of all debtors = trade receivables (current assets)
- The counterpart is the creditor (supplier the company owes money to)
- Kept in the accounts receivable subledger and condensed into the general ledger
How does a debtor arise?
A debtor arises with a sale on account: as soon as a company delivers goods or renders a service and issues an invoice with a payment deadline for it, it has a receivable – and the customer becomes a debtor. If the customer pays immediately in cash or by card, no receivable arises and therefore no debtor relationship in the accounting sense.
In accounting terms, the receivable is recorded with the outgoing invoice. The classic journal entry reads „receivables to revenue and VAT“: the debtor account is on the debit side, the revenue and tax accounts on the credit side. When payment is received, the receivable is cleared again – posted as „bank to receivables“. The balance of a debtor account thus shows at any time how much a particular customer currently still owes the company.
The debtor account in financial accounting
In double-entry bookkeeping, each customer is assigned their own debtor account. These accounts are personal accounts and are kept in the accounts receivable subledger – separate from the general ledger, into which they flow condensed via a collective account. This keeps the chart of accounts clear, while every single customer still remains traceable down to the cent.
Subledger, collective account and general ledger
Accounts receivable is a subledger (open-item accounting) of financial accounting. For each debtor it holds individual postings, open items and payment histories. In the general ledger these do not appear individually but bundled on a collective or reconciliation account „trade receivables“. The subledger and general ledger must be reconcilable at any time: the sum of all debtor balances equals the balance of the collective account. This separation allows a detailed customer-specific analysis without overloading the general ledger with thousands of individual accounts.
Debtor number and number ranges
Each debtor receives a unique debtor number. In SKR-based charts of accounts such as SKR 03 or SKR 04, the debtor accounts sit in their own number range (typically from 10000), separate from the creditors. The debtor number links accounting with the customer master record and is the key through which the ERP system and financial accounting refer to the same person. Clean, duplicate-free number assignment is therefore the basis for correct analyses and a smooth payment reconciliation.
Why accounts receivable management matters
Open receivables tie up capital: as long as a debtor has not paid, the company has indeed booked revenue but has no money in the bank. Active accounts receivable management monitors due dates, shortens the time span between invoice and incoming payment and thus lowers the capital requirement. Metrics such as the average collection period (Days Sales Outstanding) or the receivables turnover ratio make the payment behaviour of the customer base measurable.
Risk control is equally important. Through credit limits, credit checks and a structured dunning process, accounts receivable management limits payment defaults. If a receivable remains permanently uncollectible, it must be written off as a bad debt loss – doubtful receivables are individually value-adjusted in the process. Well-maintained accounts receivable is therefore not just bookkeeping but an essential building block of liquidity assurance, closely interlinked with the entire order-to-cash process.
The debtor in the ERP system
In an ERP system or inventory management system, the debtor is not isolated but consistently connected to the sales and document flow. The customer master record carries the debtor number; it runs from the quotation through order and delivery note to the invoice. When the outgoing invoice is posted, the system automatically generates the debtor posting, creates an open item and updates the account balance.
The incoming payment is – ideally via an electronic bank statement and automatic matching – offset against the open items. Dunning runs, credit limit checks and analyses of the ageing structure of the receivables also run over the debtor data. Many systems cover accounts receivable themselves or hand the postings over via a standardised interface, for example in DATEV format, to an external financial accounting system or the tax advisor. Reliable figures always require high data quality of the customer master data.
Distinction: debtor vs. creditor
Debtor and creditor are mirror-image terms and describe the same business relationship from opposite perspectives. The debtor is the party who owes – the customer who owes the company money for a delivery or service. The creditor is the party owed – the supplier the company itself still owes something to. A single invoice therefore gives rise to both, depending on the viewpoint: for the seller the buyer is a debtor, for the buyer the seller is a creditor.
Accordingly, accounting keeps two separate subledgers: accounts receivable for receivables (current assets, asset side) and accounts payable for liabilities (liability side). Memory aid: the debtor „brings“ money (from the Latin debere, to owe – the debtor owes the company), the creditor „gets“ money. Both subledgers feed different collective accounts in the general ledger.
DACH specifics and compliance
In the German-speaking region, debtor accounts are firmly tied to the common charts of accounts. In the DATEV standard charts of accounts SKR 03 and SKR 04, debtors form their own number range, which enables the seamless handover to tax advisors and DATEV. This convention shapes practically every financial accounting system in Germany and is mapped accordingly by ERP systems.
Debtor data and documents are also subject to the GoBD requirements: postings must be traceable, unalterable and complete, and open items and payment histories must be archived in an audit-proof manner. Uncollectible receivables are to be written off as a loss for tax purposes, with the VAT to be corrected accordingly. Whoever keeps debtors clean thus fulfils not only business but also commercial and tax law obligations.
Example
The debtor in everyday trade
A mid-sized B2B wholesaler delivers goods worth 8,000 euros net to a regular customer on account with a 30-day payment term. When the outgoing invoice is posted, the customer becomes a debtor: the ERP creates an open item of 9,520 euros (including 19 percent VAT) on the debtor account and posts „receivables to revenue and VAT“.
After 20 days the payment arrives. The system automatically matches the bank statement against the open item, the item is cleared and the account balance drops to zero. Had the payment failed to arrive, the configured dunning run would have automatically dunned the debtor after the due date and blocked further deliveries once the credit limit was exceeded.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Account Receivable (Debtor) in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.