Accounts payable software helps a business record and review what it owes suppliers. For a service business, a useful evaluation starts with one bill and follows it through review, a recorded payment and the remaining balance. A polished dashboard is less useful if the team cannot explain why an amount is outstanding or find the evidence behind it.
Separate the accounting record from the movement of money.
A supplier bill records an amount owed. A payment settles some or all of an obligation. Entering a bill, approving it for payment, sending money and recording that payment are distinct steps, even when a particular product places some of them on one screen.
Intuit’s instructions for entering and paying bills illustrate this distinction in QuickBooks, including recording and matching a payment. That documentation describes QuickBooks capabilities. It does not establish that FilWorx Ledger provides bank payments, document extraction or the same workflow.
Ask a prospective vendor to identify the boundary of its accounts payable software. Does it record bills and payments, initiate payments, or connect to a separate service? Confirm supported providers, permissions and fees if payment execution is offered. For a definition of the other side of the ledger, see accounts receivable versus accounts payable.
Make the bill identifiable before reviewing the balance.
Your reviewer should be able to identify the supplier, the relevant company, the supplier’s reference, the bill date, the due date, the amount and what was supplied. A description such as “monthly services” may be insufficient when several departments use the same supplier. Preserve enough context to distinguish an expected recurring bill from a duplicate entry.
Compare the bill with the evidence your business actually uses: a purchase order where applicable, a service agreement, an authorized request or confirmation that a service was received. Do not impose a purchase-order process on every transaction if your business does not use one. Decide who is responsible for resolving missing or conflicting information.
- Check whether the same supplier reference has already been recorded.
- Check the billed period and service against the agreed scope.
- Confirm which company owes the amount before recording it.
- Flag disputed or incomplete bills for review rather than silently changing the source document.
Use a worked balance instead of a dashboard promise.
The following fictional example isolates the arithmetic. It excludes tax, foreign currency and other adjustments so the reviewer can focus on whether a payment and credit relate to the same bill. Actual accounting treatment and evidence should be confirmed with your accountant.
Now ask the demonstrator to show each supporting record and the resulting payables report. If a payment belongs to another bill, it should not be subtracted just because the supplier name matches. If a credit is disputed or unrecorded, distinguish the expected adjustment from the balance currently recorded.
Fictional amounts in Philippine pesos. This is an arithmetic example, not a customer result or a FilWorx screen.
- ₱12,000 supplier bill
The accepted bill establishes the amount to review.
- ₱4,000 recorded payment
The payment is supported and applied to this bill.
- ₱1,000 supplier credit
The credit is validated and applied to this bill.
Remaining balance: ₱12,000 − ₱4,000 − ₱1,000 = ₱7,000. Check the supporting records before accepting the result.
Decide who records, reviews and authorizes.
The U.S. Government Accountability Office’s Green Book is a primary reference on internal control. Its 2025 revision took effect for federal agencies in fiscal year 2026. It is a U.S. federal standard, not a Philippine private-sector requirement; its focus on reliable reporting and control design is useful background for framing review questions.
For your own business, list the person who creates supplier records, the person who records bills, the person who reviews exceptions and the person authorized to release money. Where a small team combines responsibilities, ask your accountant what independent checks are practical. A permission setting is useful only if the operating process follows it.
Confirm how supplier bank-detail changes are verified through a trusted process. Do not treat an email requesting a new account as sufficient authorization. This is an operational control question, not a claim that the accounting software detects fraud or validates bank ownership.
Check due dates, exceptions and the reporting date.
An outstanding balance and an overdue balance answer different questions. A report needs a clear reporting date and an understandable basis for due dates. Test a bill that is not yet due, one that is overdue and one that is partially paid. Check how credits and disputed amounts appear without assuming every report uses the same categories.
If several companies are managed in the same environment, confirm that the selected company and reporting period are visible. Ask how the payables detail reconciles to the accounting records and how a late entry is reviewed after a period has been prepared for close. The month-end close checklist places this review alongside other accounting checks.
| Scenario | Question to answer |
|---|---|
| Possible duplicate | Can the reviewer find the existing supplier reference? |
| Partial payment | Does the remaining amount agree with the supporting entry? |
| Supplier credit | Can the reviewer trace the credit to the affected bill? |
| Overdue bill | Is the report date clear, and is the due date correct? |
| Company context | Are the bill and report being reviewed for the right company? |
Evaluate FilWorx Ledger using the same records.
FilWorx Ledger covers supplier bills, invoices, journals and financial reporting. Bring a fictional supplier bill, partial payment and credit scenario to confirm how the relevant records and reports are handled in the available package.
Confirm the specific recording steps, permissions and outputs in a demo. Do not assume payment execution, automated approvals, bank integrations, tax filing or document extraction unless separately verified. A sound purchasing decision records both demonstrated capabilities and the manual controls your team will retain.
Sources & further reading.
Further reading from the original publishers. Product documentation describes that publisher’s product; it does not establish FilWorx capabilities.