Accounts Payable, Accounts Receivable, and Invoicing

Accounts payable and accounts receivable are more than two balance-sheet accounts. Together, they form the operating path between delivering work, collecting customer cash, accepting vendor obligations, and releasing payments. When that path is controlled, a business can see what it expects to collect, what it has committed to pay, and which exceptions need attention.

A bank balance cannot provide that view by itself. It shows cash after activity has happened. A reliable AP and AR process shows the commitments around cash before they settle. The goal is not merely to enter invoices and bills. It is to create a cash-conversion system in which each document has an owner, each balance has support, and each exception has a next action.

How AP, AR, and cash fit together

Accounts receivable, or AR, records amounts customers owe for goods or services already provided. Accounts payable, or AP, records amounts the business owes suppliers for goods or services already received. Invoicing creates much of the receivable record. Bill capture and approval create much of the payable record.

These balances are not interchangeable with cash. Revenue can be recorded before the customer pays, and an expense can be recorded before the vendor payment leaves the bank. That timing difference is the reason a profitable month can still feel tight and a comfortable bank balance can still be committed to upcoming bills.

The useful question is not only “How much cash do we have?” It is also:

• Which customer invoices are open, disputed, overdue, or likely to be collected soon?
• Which vendor bills are approved, scheduled, blocked, duplicated, or missing?
• Which deposits and withdrawals have not been matched to their source documents?
• Which credits, prepayments, retainers, or partial payments change the apparent balance?
• Which commitments fall inside the period covered by the cash forecast?

The ledgers answer those questions only when transactions are recorded at the right level of detail and reconciled to outside evidence.

The invoice-to-cash workflow

A dependable AR process begins before the invoice is sent. Customer details, billing contacts, purchase-order requirements, payment terms, tax treatment, and delivery evidence should be clear enough that the invoice can pass the customer’s approval process.

Create the invoice from approved information

The invoice should agree with the contract, order, milestone, time record, or other source that authorizes billing. Use consistent customer names and item or service descriptions. Include the information the customer needs to route and approve the bill. A correct invoice sent to the wrong contact can age just as badly as an incorrect invoice.

Confirm delivery

Sending is not the same as delivery. Record the date and method, then confirm that the invoice reached the intended system or person. Portals, spam filters, missing attachments, and rejected purchase-order fields can stop the process before the customer begins its review.

Monitor the open-item list

An AR aging report groups unpaid invoices by age. It should be treated as a work queue, not merely a month-end report. Each material past-due item needs a status: reminder sent, customer reviewing, documentation requested, dispute open, payment promised, credit pending, or escalation required.

Apply collections accurately

Customer cash should be matched to the correct invoices and credits. A net processor deposit may contain gross sales, fees, refunds, and timing differences. Posting the deposit directly to revenue can leave invoices open and distort both revenue and fees. Use processor or remittance detail to bridge the gross activity to the bank.

Reconcile AR

The AR control balance in the general ledger should agree with the detailed customer aging. Differences can arise from journal entries posted directly to the control account, deleted documents, incorrect dates, or payments left unapplied. Reconciliation connects the financial statement balance to the customer-level evidence.

The purchase-to-payment workflow

AP control begins before cash is released. The process should establish that the vendor is valid, the business received what it is paying for, the amount is correct, the coding is appropriate, and an authorized person approved the payment.

Maintain controlled vendor records

Use one clean vendor record for each supplier and establish who can create or change it. Duplicate names and rushed edits can produce duplicate bills or direct a payment to the wrong destination. Changes to sensitive payment information deserve an independent verification step using a trusted contact path.

Capture bills consistently

Bills arriving through personal inboxes, text messages, paper, and portals are easy to miss. Route them into one documented intake process. Record the vendor invoice number, date, due date, amount, account coding, project or class detail, and supporting document.

Check the obligation

Before approval, compare the bill with the purchase authorization, contract, receipt, or service confirmation that supports it. The exact evidence depends on the purchase. The principle is consistent: the person approving payment should have enough information to know what was purchased, whether it was received, and whether the charge agrees with the arrangement.

Approve and schedule separately

Approval confirms that the business accepts the obligation. Scheduling determines when to release cash. Keeping those steps distinct helps the business protect due dates, discounts, disputes, and cash priorities without rewriting the underlying bill.

Release and record the payment

Payment authority should not rest solely with the person who creates vendors, enters bills, and reconciles the bank. Even a small team can preserve some separation through owner approval, bank controls, payment reports, or an after-the-fact review by another authorized person.

Reconcile AP

The AP control account should agree with the vendor aging. Also review vendor statements when available, old credits, negative balances, duplicate amounts, and bills marked paid without a corresponding bank transaction. The aging should represent real, supported obligations at the reporting date.

Worked example: connecting the ledgers to cash

All figures in this example are illustrative. They demonstrate the workflow and are not a benchmark, forecast, or recommendation.

Suppose a design firm begins the week with $28,000 in the bank. Its AR aging shows $42,000 open: a $12,000 invoice expected this week, a $20,000 invoice waiting for customer approval, and a $10,000 invoice under dispute. Its AP aging shows $31,000 open: $9,000 approved for this week, $14,000 due later, $5,000 waiting for internal approval, and a $3,000 vendor credit that has not been applied.

Looking only at the bank suggests $28,000 is available. Looking only at total AR suggests another $42,000 may arrive. Neither view is suitable for an immediate payment decision.

The short-term operating view starts with the $28,000 bank balance, adds only the $12,000 collection supported by a credible payment status, and subtracts the $9,000 of approved near-term payments. That produces an illustrative $31,000 position before other payroll, card, tax, or operating cash movements. The $20,000 customer invoice remains a timing risk, the $10,000 disputed invoice is not treated as available cash, and the $5,000 unapproved bill remains an unresolved obligation rather than disappearing.

Now assume the $12,000 customer pays through a processor that deposits $11,640 after a $360 fee. The bookkeeper applies $12,000 to the invoice, records the $360 fee, and matches the $11,640 deposit. Posting only the net bank deposit to revenue would understate the sale, omit the fee, and leave the customer invoice open.

On the payable side, the team applies the $3,000 vendor credit before scheduling the related payment. That step keeps the payment file, vendor ledger, and cash plan aligned. The example shows why AP and AR need statuses and reconciliation, not just totals.

Controls that make the process usable

The best control is one people can follow repeatedly. A complicated approval chart that everyone bypasses offers less protection than a short workflow with clear ownership.

Use named states

Give invoices and bills a small set of defined statuses. AR might use draft, sent, delivered, disputed, promised, paid, and written off with approval. AP might use received, matched, awaiting approval, approved, scheduled, paid, and blocked. A state should tell the next person what must happen.

Preserve evidence

Attach or link the invoice, bill, approval, remittance, credit, and relevant correspondence to the accounting record or an organized document system. The evidence should allow another person to understand the balance without reconstructing the story from memory.

Separate recordkeeping from cash authority

The person maintaining the ledger can prepare a payment proposal, but an authorized business owner or manager can review and release it. On the customer side, a person issuing credits should not be able to hide the effect through unsupported write-offs.

Review exceptions, not only totals

Totals can appear reasonable while individual items are stale or wrong. Review old invoices, unapplied cash, customer credit balances, negative vendor balances, duplicate invoice numbers, round-dollar amounts, missing approvals, and manual entries to control accounts.

Close with reconciliations

At month-end, reconcile the bank, payment processors, AR detail, AP detail, credit cards, and other relevant accounts. Then preserve the reports used for the close. A live report can change after the fact, so the retained close package should show what was reviewed.

Turning aging reports into action

An aging report is useful when it distinguishes accounting age from collection reality. Due dates provide a starting point, but collection notes explain whether an amount is expected, disputed, offset by a credit, or waiting on documentation.

For AR, assign a next action and owner to each important overdue item. Grouping every item under “follow up” hides the difference between a missing invoice, a customer dispute, and a promised payment. Track the reason so recurring billing problems become visible.

For AP, use the aging to plan cash without changing valid due dates merely to fit a preferred report. Separate approved bills from disputed or unapproved items. Preserve credits and partial payments so the amount proposed for payment reflects the vendor ledger.

A short rolling cash view can connect the two reports. Use collection status and payment approval, not wishful timing. The forecast should be updated when facts change and reconciled to actual cash movements afterward.

How the AP and AR process goes wrong

Invoices are created after the work is finished, then sent late

The collection clock starts late because billing depends on memory or a rushed month-end search. Define the event that authorizes billing and create a recurring review of completed work, milestones, shipments, or approved time.

A net deposit is treated as the entire sale

Processor fees, refunds, and multiple customer payments disappear inside one bank amount. Reconcile the processor detail from gross activity to the net deposit and apply customer payments to the correct invoices.

Vendor records are duplicated

The same supplier appears under variations of its name, so bills, credits, and payment history split across records. Restrict vendor creation, search before adding, and merge or deactivate duplicates through a controlled cleanup.

Credit balances are ignored

A customer overpayment or vendor credit remains on the aging and is not considered in the next transaction. Review negative and credit balances separately, investigate their source, and apply or resolve them with support.

The aging is stale

Invoices and bills remain open after settlement because payments were not applied, dates were changed, or entries were posted outside the subledger. Reconcile the detailed aging to the general ledger and investigate each difference.

The cash forecast assumes every due date will happen

Customer due dates are treated as guaranteed collections, while unapproved or disputed bills are treated as if they do not exist. Use documented status and a range of possible timing where uncertainty matters.