Supplier bills overview
Create, approve, pay and track supplier bills inside Accounting while maintaining vendor, tax and ledger connections.
What this feature does
Create, approve, pay and track supplier bills inside Accounting while maintaining vendor, tax and ledger connections. It forms part of Britixo Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.
How the module flow works
The module includes bill list, create/edit, preview, attachments, delete and approve-payable actions plus a separate Pay Bills workspace.
Bills can contain expense-style and item-style lines with debit and credit account context.
When the Purchase module is active, supplier invoice workflows can also originate there; avoid entering the same liability twice.
Step-by-step workflow
- Open Bills and filter by vendor, status or due date.
- Open a bill and review source document, lines, tax and totals.
- Confirm approval status.
- Use Pay Bill for approved payable amounts.
- Review payment allocations and attachments.
- Check Accounts Payable ageing.
- Reconcile the payment account.
Important fields and decisions
What happens after completion
After the action is saved, Britixo keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.
- Open the saved record and confirm its final status.
- Review the source reference and every debit and credit line where ledger data was created.
- Use the relevant register, ageing, reconciliation or report to verify the wider effect.
Controls, checks and common mistakes
- Do not pay draft or unapproved bills.
- Avoid duplicate vendor invoice numbers.
- Review due dates and payment terms.
- Protect supplier bank details.
- Use the least destructive correction available and record the reason for material changes.
- Do not bypass a permission, approval or closed-period control by changing unrelated data.
