Tipalti rolls out integrated treasury and payables visibility

What Tipalti announced

Tipalti announced the rollout of Tipalti Treasury on 26 October 2026, following its acquisition of Statement in 2025. The company describes a platform combining bank balances and transactions with accounts payable information, including customizable thirteen-week cash forecasts using bank and ERP data. Its announcement targets growing mid-market businesses managing multiple entities, banks and currencies. The release describes the product's intended capabilities; it does not establish that every bank connection, merchant entity or forecasting requirement is supported. Businesses must confirm coverage and commercial terms for their own implementation.

A useful dashboard must lead to a specific decision

For a merchant, cash visibility becomes valuable when it changes a decision before the payment deadline. An accounts payable team may see invoices ready for release while treasury sees expected acquiring settlements that have not arrived. Combining those views can help identify a timing gap, but the quality of the decision still depends on how each number was produced. The analysis below sets out a practical evaluation approach rather than a product performance claim.

Choose a concrete decision for the initial assessment. It might be whether to release tomorrow's supplier batch, fund a refund account or transfer money between approved operating accounts. Define the information needed, the person authorized to act and the deadline. This prevents a visually impressive consolidated balance from becoming the project's only measure of success.

Distinguish displayed balances from spendable money

A merchant may have several amounts that appear positive but serve different purposes. Processor receivables, bank balances, reserves and funds allocated to upcoming refunds should not automatically be treated as interchangeable. Build a cash classification that reflects actual access and contractual restrictions. The person approving a payment needs to understand what can be used, not merely what appears somewhere in a financial system.

Set rules for transfers in progress so the same funds are not counted at both ends. Preserve the source account, destination account, instruction time and confirmation status. If one feed updates before another, the consolidated view should expose that timing difference. A temporary mismatch deserves an explanation; silently adjusting it to make totals look tidy removes useful evidence about the underlying process.

Map the coverage before connecting every account

Begin with an inventory of legal entities, accounts, currencies and payment providers. For each connection, record the expected information, refresh pattern, access permissions and reconciliation owner. Confirm whether the data includes pending items, completed transactions or both. Similar labels across two banks can conceal different meanings, so establish the interpretation before combining their balances into a management report.

Prioritize accounts that support the chosen operating decision. A limited implementation with understood coverage may be more useful than a broad rollout with unexplained omissions. Keep a visible list of accounts outside the system and how their balances enter the decision process. Otherwise, staff may assume that a consolidated screen is complete simply because it displays a group total.

Forecast acquiring settlements as uncertain receipts

Merchants should distinguish scheduled receipts from money already received. An acquiring settlement may depend on processing cutoffs, adjustments, refunds or other contractual conditions. Use the actual provider reports and agreement to determine how the forecast should represent these items. Avoid hardcoding a universal settlement delay merely because it fits one account's recent experience.

Create separate scenarios for the expected receipt date and a plausible delay. Then identify which planned payments would become difficult under the second scenario. Finance can use that information to arrange a lawful funding response or adjust discretionary expenditure before the deadline. The objective is a manageable decision process, not a forecast that appears precise while hiding its largest timing assumptions.

Connect payable status to payment authority

An invoice appearing in a cash forecast does not necessarily mean it is approved for payment. Separate receipt, validation, approval, scheduling, submission and completion. Each status should have a defined meaning and an accountable owner. If a payment is cancelled or returned, the forecast should reflect the revised obligation without creating a duplicate invoice or losing the original audit trail.

Pay particular attention to changes made near the release deadline. A revised bank account, disputed delivery or amended invoice may require renewed review. Treasury visibility should help staff understand the consequence of a hold, while the authorization process determines whether release is permitted. Do not let a desire to improve a projected cash position override supplier verification or payment approval controls.

Explain differences instead of hiding them in adjustments

Test the system with a completed period for which the business already understands its cash movements. Compare opening balances, receipts, payments, transfers and closing balances with the source records. Investigate differences by category: missing data, timing, currency translation, duplication or classification. A single balancing adjustment can conceal several unrelated issues and make the next forecast harder to trust.

Keep assumptions separate from observed transactions. When staff revise an expected settlement date, retain the previous assumption, the reason for change and the approving person where appropriate. That history helps explain why a forecast changed between management meetings. It also supports learning: repeated differences may reveal a weak assumption that deserves a better method rather than another manual correction.

Measure whether the operating decision improves

Choose evaluation measures tied to work the finance team actually performs. Examples include the time needed to prepare a funding decision, the number of unexplained balance differences and the frequency of urgent transfers caused by missing information. Define a baseline before implementation. This allows the merchant to assess whether the tool changes its operating workload rather than relying on a general impression of convenience.

Include adverse cases in the trial. Test an unavailable feed, a returned supplier payment and a settlement arriving later than forecast. Staff should know how to recognize stale information and continue safely through an approved fallback. A successful normal-day demonstration is useful, but it does not show how the business will operate when information is incomplete.

Keep forecasts understandable to the people who approve payments

A forecast should show which parts come from source records and which parts depend on judgment. Give each important assumption an owner and a review date. For example, a sales projection supplied by the commercial team should remain distinguishable from an issued invoice and from a bank receipt. Combining those items into one number may be convenient, but the approval team still needs to understand their different degrees of certainty.

Use a brief review meeting to examine changes that would alter a funding decision. Focus on a small set of exceptions: a large receipt moving later, an unexpected payable becoming due, or a currency balance falling below the amount needed for approved payments. Record the decision and its supporting assumptions. When the next update arrives, compare the result with that record. This creates a practical feedback loop without requiring staff to debate every small variation in the forecast. Clear explanations also make it easier for a backup colleague to act when the usual treasury owner is unavailable, reducing dependence on knowledge held by one individual. Keep that explanation alongside the payment approval for later internal review.