Skip to main content
    ← Back to the knowledge hub

    Accounting from the source

    Cash outflow is not the same as expense: advances, transfers and grouped payments

    Separate cash movement from accounting meaning and trace party, reference, document and allocation before classifying the transaction.

    By Linda Accounting ITPublished 6 minute approximate read

    At month-end it is tempting to see a THB 50,000 outflow and ask which expense account to use. The prior questions are who received it, which event caused it and which order, invoice or outstanding balance supports it. Jumping directly from bank line to expense can collapse different economic events into one label.

    This is process-design guidance rather than an accounting or tax determination for any specific transaction. Treatment still depends on the underlying facts and the organisation’s policy.

    Separate cash movement from expense meaning

    ERPNext Payment Entry supports receipts, payments and internal transfers, as well as advances, partial settlement and one payment allocated across several invoices. This is a useful illustration that one cash movement can have several business meanings.

    Use the bank line to locate context first: supplier payment, reimbursement, advance, owner transfer, tax payment, refund or internal transfer. Then follow the evidence to the approved accounting treatment.

    References: [1]

    Keep advance payments traceable until later allocation

    An advance is paid before the final invoice or complete delivery. Keep the party, related order or commitment, bank reference and amount so later allocation does not depend on guessing from the payment value.

    ERPNext Advance Payment Entry allows an advance to remain linked to a party and optionally an order, then be allocated later through reconciliation or invoice workflow. The design lesson is not to bury advance cash in a generic expense merely because the money has left the bank.

    References: [2]

    An internal transfer needs two linked sides

    Moving money from bank A to bank B within the same business reduces one balance and increases another without creating a new supplier expense. Preserve a shared transfer reference, date, amount and destination so the two sides can be matched.

    ERPNext exposes Internal Transfer as a distinct Payment Entry type, illustrating why a negative statement amount alone is not enough to classify the business meaning.

    References: [1]

    One bank line can settle several invoices—and one invoice can be paid several times

    A THB 120,000 transfer may settle three supplier invoices. Creating another expense from the bank line would duplicate the event if those invoices already created payables. Allocate the payment to outstanding records and keep unallocated differences explicit.

    ERPNext Purchase Invoice creates the payable and ledger effect on submission, while payment is handled later through Payment Entry or reconciliation. This demonstrates the difference between a purchase obligation and its cash settlement.

    References: [3]

    A useful review order: party → reference → document → allocation → account

    Identify counterparty and reference, locate order/invoice/claim evidence, check for an existing voucher, allocate the money correctly, then investigate any amount still unsupported. Avoid creating a new expense merely to clear an unmatched statement line.

    When evidence is insufficient, use an exception status with an owner and follow-up date. A reviewable close preserves both cash evidence and transaction lineage.

    A practical starting checklist

    • Separate bank movement from accounting meaning.
    • Link advances to party and commitment.
    • Match both sides of internal transfers with one reference.
    • Allocate grouped and partial payments to existing invoices.
    • Keep unexplained outflows in an exception queue instead of guessing expense.

    Apply it to your business

    The statement tells you that cash moved; workflow and evidence explain why. A traceable close connects those layers without automatically turning every cash outflow into expense.

    References

    1. Frappe. (n.d.). Payment Entry. Retrieved October 1, 2026.
    2. Frappe. (n.d.). Advance Payment Entry. Retrieved October 1, 2026.
    3. Frappe. (n.d.). Purchase Invoice. Retrieved October 1, 2026.

    Numbered references support the attributed statements. Scenarios and recommendations are Linda’s examples, not verified client outcomes.

    This article provides process-design guidance and illustrative examples, not an accounting, tax or legal determination or certification of every software module. Apply it with regard to your business, permissions and actual system scope.