Count the kinds of work, not just the bills
A business evaluating BILL and Tipalti should classify its payables before comparing proposals. Paying 1,000 familiar domestic suppliers is a different workload from onboarding 1,000 new international payees with varied currencies and information requirements. Both the volume and the kind of exception matter, but a transaction count alone will not identify the better setup.
BILL describes invoice workflows, approval routing, payment activity, and controlled access. Tipalti describes accounts payable together with supplier onboarding, invoice matching, multi-subsidiary and currency workflows, and broader payout use cases. That is a reason to inspect the proposed operational scope carefully. It is not evidence that every feature is included, available in every country, or a replacement for professional tax decisions.
References: BILL: Accounts payable software; Tipalti: Accounts payable and supplier management
Separate supplier invoices from mass payouts
Some businesses use the same word payables for very different obligations. A supplier invoice follows a purchasing and approval process. A creator royalty, marketplace earning, or partner commission may be calculated from activity data before a payment exists. Determine whether your project needs invoice processing, calculated payouts, or both.
If payouts are calculated elsewhere, name the system that owns the calculation and the person who approves the final amount. The payment platform should receive an approved obligation with an identifier that can be reconciled. It should not become the place where staff quietly adjust earnings to make a payment file upload. Compare the vendors on the actual workflow proposed for each obligation, including correction and dispute handling.
References: Tipalti: Accounts payable and supplier management
Give onboarding its own acceptance criteria
Supplier setup determines whether finance can safely pay the right party and explain the transaction afterward. List the information required for your supplier groups: legal name, entity relationship, country, currency, payment details, and any tax documentation your adviser determines is needed. Keep data collection separate from the professional conclusion about a payment's treatment.
Tipalti documents self-service supplier onboarding. During evaluation, ask who verifies submitted information, what happens when information conflicts, and which changes trigger a new review. Ask BILL to demonstrate the corresponding process in its proposed arrangement. Use a supplier that changes bank details while an invoice is awaiting approval. The workflow should make the change visible without forcing the AP clerk to maintain an unofficial checklist in a separate inbox.
Include a supplier that becomes inactive while a valid obligation remains unpaid. The team needs a way to review and settle that obligation without losing the earlier approval record or reopening the supplier for unrelated new purchases. Ask how that distinction appears to the person preparing the run.
References: BILL: Accounts payable software; Tipalti: Accounts payable and supplier management
Build the comparison around your exception mix
A useful requirement describes both the routine event and the difficult case. Use the table as a starting point, then replace the examples with the exceptions your staff already handles.
| Requirement | Case to demonstrate |
|---|---|
| Supplier onboarding | Missing information, conflicting details, and a banking change |
| Invoice approval | A changed invoice after one approver has signed off |
| Entity allocation | An invoice shared across entities with a documented allocation |
| Currency payment | Quoted conversion, recipient amount, and the accounting record |
| Payment failure | A returned payout without a second expense or duplicate obligation |
| Close evidence | Open obligations and payments tied back to approved source records |
Check country coverage at the transaction level
A vendor's international reach does not mean every combination of sending entity, recipient country, currency, and payment method is available. Give each finalist a sample of the routes you actually need and request written confirmation of availability, prerequisites, charges, and expected timing. Keep new or unusual routes visible as exceptions until they are confirmed.
Ask who bears intermediary or recipient charges and how a rejected or returned payment is reported. Determine whether the ledger receives the original obligation, conversion difference, payment fee, and returned balance separately. These details affect supplier conversations and reconciliation. They also help you compare the cost of the actual route rather than a low fee that applies to a different currency or method.
References: BILL: Accounts payable software; Tipalti: Accounts payable and supplier management
Buy the operating model you can support
Compare implementation, required modules, users, transaction costs, supplier onboarding work, and continuing support. Estimate internal effort from your own exception sample. A wider platform can be justified when it removes real fragmentation across entities and payee types. It can also add unnecessary setup if the business only needs a controlled domestic bill-payment process.
Require the selected vendor or partner to explain who owns an issue that begins in the source system, passes through approval, and fails during payment. That ownership should continue after launch. Choose between BILL and Tipalti once you can trace an approved obligation through settlement and into the books, including the failed cases. The clearest proposal is the one that makes the remaining responsibilities visible and assigns them to people who can perform them.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.