Approving a supplier invoice even though the delivery was short, or spotting an overdue receivable only after 90 days: both trace back to accounts payable and accounts receivable, the core of financial management. This article covers how the two differ and how to manage each with controls that actually work.
In short: accounts payable is what a company owes suppliers for goods or services already received but not yet paid for. In Indonesian it is called utang usaha, and it is recorded as a current liability. Accounts receivable (piutang usaha) is the mirror image: the right to collect on credit sales a customer has not yet paid, recorded as a current asset.
Accounts payable and accounts receivable are two sides of the same transaction. What you record as a payable to a supplier appears as a receivable in that supplier's books for the same invoice. The difference lies in whether you are the buyer or the seller, and every other distinction follows from that.
|
Position on the balance sheet |
Current liability |
Current asset |
|
Direction of cash |
Out |
In |
|
Counterparty |
Supplier/vendor |
Customer |
|
Triggering document |
An invoice received from a supplier |
An invoice issued to a customer |
|
Parent process |
Procure-to-Pay |
Order-to-Cash |
|
Common metric |
DPO (Days Payable Outstanding) |
DSO (Days Sales Outstanding) |
|
Main risk |
Paying twice, or paying for goods that never arrived |
Bad debt |
Because the positions are opposite, so are the controls: accounts payable is controlled before payment, accounts receivable after the invoice has been issued.
Managing accounts payable rests on verifying three documents before any payment is made. Once cash has gone out, correction is only possible by claiming it back from the supplier, which costs far more than holding an invoice for verification. The control has to sit before payment.
Material from SAP Learning defines three-document matching (three-step verification, known outside SAP as a three-way match) as comparing the following three documents before an invoice is approved.
If item, quantity, and price all agree, the invoice can be paid. If not, it is held for review. Payment goes out only once there is no discrepancy and no payment block. For services with no goods receipt, matching two documents is usually enough.
Terms notation such as 2/10 net 30 means a 2% discount if paid within 10 days, with the full amount due in 30. Payment should follow the agreed schedule rather than going out as fast as possible.
Delaying payment can lift the cash balance temporarily, but it risks losing discounts and prompting suppliers to tighten terms in future.
On the receivables side, control works after the invoice has been issued, because the money already sits with someone else. The measure that matters is the age of the receivable, not the total. Rp1 billion outstanding at 20 days is healthy; if half of it is more than 90 days old, that is cause for concern. Each age bracket calls for a different response:
|
0–30 days |
Not yet due / recently past due |
Automated reminder, no escalation |
|
31–60 days |
Late |
Personal contact with the customer's payments team |
|
61–90 days |
Problematic |
Escalate to management; hold shipments and new orders |
|
>90 days |
At risk of default |
Review as potentially uncollectible; consider formal channels |
The age brackets are flexible and can be adjusted by each company. The grouping exists to trigger action, not merely to report. A receivable moving into the next bracket is a signal that something needs doing.
The best prevention is setting credit limits and payment terms before an order is accepted, not during collection.
In an ERP (Enterprise Resource Planning) system, accounts payable and accounts receivable are sub-ledgers that update the general ledger automatically as documents are posted. Questions about how much is owed to a supplier, and whether that agrees with the general ledger, can then be answered on the spot.
Both are standard sub-modules within the SAP finance module (FICO). According to SAP Learning, Accounts Receivable in Financial Accounting (FI) records and manages accounting data for every customer, and the assigned reconciliation account (reconciliation account) is updated automatically. Customer master data holdspayment termsanddunning terms, so collection follows agreed rules rather than staff memory.
The primary duty of accounts payable staff is to ensure payment is made only against verified invoices. They check supplier invoices against three documents (purchase order, goods receipt, and invoice), schedule payments according to terms, and reconcile supplier balances. Invoices that do not match are held for review.
A liability. Accounts payable is a current liability because it is settled within the company's normal operating cycle, while accounts receivable is a current asset generally realized within twelve months after the reporting period. Both are balance sheet items rather than income statement items: what reaches the income statement is the purchase and the sale, not the outstanding balance.
Accounts payable arises from buying operational goods or services on credit, with no formal loan agreement, and is generally interest-free as long as it is paid within agreed terms (30 days, for example). A bank loan comes from a credit agreement, carries interest, and has a fixed term. Both are liabilities, but only accounts payable follows the rhythm of daily operations.
Accounts payable and accounts receivable are two sides of the same transaction, which is precisely why they must be managed differently: payables are controlled before cash leaves, receivables are managed by age. Soltius, part of Metrodata Group since 1998, has extensive experience implementing and supporting SAP S/4HANA Finance, including the design of payables and receivables processes. That work usually begins with an assessment of the systems currently in place.
For more on structuring payables and receivables processes with SAP S/4HANA Finance at your company, visit soltius.co.id.