Frequently asked questions

Listra is an AP platform that resolves invoice exceptions end-to-end. It captures the invoice, matches it against the PO, goods receipt, and contract, identifies the exception, gathers the evidence, communicates with the vendor where needed, applies your policy, and posts to your ERP. The work that other AP tools route to your team for manual resolution is the work Listra is built to do.

Most existing AP tools were built around invoice capture, OCR, and workflow routing. They digitize the easy part and pass the hard part (the discrepancies, the vendor follow-up, the policy decisions) back to the AP team. Listra was built around exception resolution from the ground up. The investigation, the vendor loop, and the resolution against policy are the product, not the feature on top.

No. Listra changes what the AP team spends its day on. Instead of researching mismatches and chasing vendors, the team reviews resolutions, oversees outcomes, manages strategic vendor relationships, and works on what their tools have been keeping them from. Most of our customers process more volume with the same team after deploying Listra rather than reducing headcount.

You do. Listra executes your AP policy. You define the rules, the tolerance bands, the approval thresholds, the escalation paths, and the exception types Listra is allowed to resolve without human approval. Listra follows that configuration. Every action is logged with the evidence and the rule that was applied.

An invoice arrives through email, upload, API, or EDI. Listra captures it and pulls the related PO, goods receipt, contract, vendor history, and policy in one investigation. If a discrepancy is detected, Listra identifies the root cause, drafts a vendor message if one is needed, applies the resolution your policy authorizes, routes any required approvals, and posts to your ERP with the evidence pack and the audit trail attached.

Quantity variances, price variances against PO and against contract, partial shipments, freight overcharges, duplicate invoices, missing or delayed goods receipts, missing PO references, non-PO invoices, vendor master mismatches, quality rejects requiring credit memos, currency conversion discrepancies, tax variances, and contract pricing tier changes are all in scope. The platform is designed to handle complex cases first; the simple ones become trivial as a result.

No. Listra handles both PO-based and non-PO invoices. Non-PO invoices route through coding, validation, and approval against your chart of accounts and your approval matrix. The platform does not require every vendor to be on a PO process.

During implementation. You configure the policy rules: tolerance bands, approval thresholds, escalation paths, GL coding rules, vendor-specific terms, and the exception types Listra is allowed to handle in Autopilot. The configuration is reviewable, editable, and versioned. Policy changes take effect immediately.

Yes, in your team's voice and from your domain. Listra drafts vendor messages and sends them under your AP team's email identity. Vendors respond to your inbox; Listra reads the response and proceeds. In Copilot mode, your team reviews messages before they go out. In Autopilot mode, Listra sends the message once your policy authorizes it on that exception type.

Copilot is the mode in which Listra does the work and waits for your AP team to approve. It investigates the exception, gathers the evidence, drafts the vendor message, and recommends the resolution. Your team reviews and approves before any action is taken. Autopilot is the mode in which Listra executes the resolution against your policy without human approval, while still logging the full audit trail. You choose which exception types run in Autopilot and which stay in Copilot.

Most customers start in Copilot across all exception types. As the audit trail proves consistent on a given type (typically partial shipments and freight audits first), you move that type to Autopilot at your pace. The graduation is exception type by exception type, not all-or-nothing.

Yes, at any time, by exception type or across the board. There is no rip-and-replace and no commitment to a particular autonomy level.

It escalates. If Listra cannot identify the root cause, cannot find an authoritative resolution under your policy, or encounters a confidence below the threshold you set, it routes the exception to your AP team with the evidence it has gathered, the resolution paths it considered, and a recommended next action.

No. Copilot replaces the manual investigation work, not the decision authority. The AP specialist or AR manager still reviews and approves. Most customers run more volume with the same team after deploying Listra rather than reducing headcount.

Most reviews take seconds because the analysis and evidence are already prepared. A reviewer scans the recommended action, glances at the evidence pack, and approves. Exceptions that need deeper investigation get the time they deserve.

Yes. Role-based access control sets who can approve what. Approval thresholds by amount, by document type, by entity, and by GL category are configured in your policy.

The reviewer declines or edits. Listra learns from declines and corrections. The audit trail captures the override and the reason.

Yes. Copilot and Autopilot are configured per exception type within each module. A customer might run Copilot on dispute resolution and Autopilot on invoice delivery within the same AR deployment.

Duplicate detection, routine quantity and price matching, standard invoice delivery, routine cash application, and dunning cadence are typical first migrations. Vendor invoice exception resolution and routine deduction validation usually follow.

The policy, the Autopilot scope, the confidence thresholds, and the bounded writeback controls. Anything outside any of these routes to a human.

Configure the confidence threshold to escalate borderline cases. Configure the amount threshold to keep larger cases in Copilot. Both can be tightened or loosened at any time.

Yes. The audit trail is the same in Autopilot as in Copilot: every action, every evidence source, every rule applied, every system or user that approved. SOX 404 evidence and SOC 2 evidence are built from the same log.

Update the policy and the new rules apply to the next case immediately. The audit trail captures the policy version that was in effect for each historical case.

NetSuite and QuickBooks Online are the supported standard connectors today. Xero, Sage, and Bill.com are on the near-term roadmap. If your environment uses one of these, standard implementation is included at no additional cost.

Yes, through a custom integration engagement scoped as a one-time professional services fee. The scope depends on the system: a light data feed, a customer API integration, a new ERP connector, or a more complex multi-system program. We scope and price the integration as a separate statement of work.

Standard supported connectors are configured during onboarding and you are live within roughly one week. Custom integrations take longer; the engagement scope determines the timeline.

Listra is preparing for formal SOC 2 audit. Our security questionnaire and data processing addendum are available on request to qualified prospects.

Customer data is stored in US AWS regions by default. EU data residency is available on request and is on the roadmap for self-serve selection.

Multi-tenant architecture with company-level data isolation enforced at the API, database, and query layers. Your data is logically segregated from every other Listra customer at every layer of the platform.

Yes. SSO through your identity provider. MFA on high-value approvals. Role-based access control with permission categories defined at the action level, not just the page level.

Every action Listra takes is logged with a timestamp, the data source it consulted, the policy rule it applied, the resolution it executed, and the user (or system) that approved it. The log is immutable, exportable, and available to your internal audit, your external auditors, and your finance leadership at any time. The audit trail is SOX-ready by default.

AES-256 at rest. TLS 1.2 or higher in transit. Network segmentation and continuous monitoring on AWS infrastructure.

Roughly one week on a standard ERP connector. We connect the ERP, import the vendor master and chart of accounts, configure your AP policy, set up your approval matrices, and run a parallel period on real invoices. Custom integrations add time depending on scope.

Our team. Standard implementation is included at no additional cost when you use a supported accounting system and standard configuration. This covers environment setup, connector configuration, AP and AR email routing, user setup, workflow configuration, training, and go-live support.

Yes. A thirty-day pilot is available at no cost, capped at 100 AP documents and one entity. The pilot is designed to prove the resolution path on your actual invoices and your actual policy. At the end of the pilot you can convert to a Starter subscription or step away.

AP is priced per processed AP document, with a monthly Starter floor and tiered rates that descend as annual volume grows. AR is priced per active case-month managed by Listra. The AP + AR bundle is offered at a combined monthly floor with each module priced at its standard rate. Standard implementation is included; custom integrations are scoped separately. Reach out for pricing specific to your environment.

Standard implementation is included at no charge when you use a supported accounting connector. Custom integrations, EDI feeds, new ERP connectors, and non-standard systems are scoped as one-time professional services in a separate statement of work.

A ten percent discount is available on annual prepayment for Growth tier and above. Monthly billing is standard on the Starter tier.

Pricing is built so that there are no cliffs at tier boundaries. Customers near a boundary pay roughly the same amount whether they are in the lower or upper tier, and Growth tier and above allow up to ten percent of unused annual volume to roll over for ninety days. Quarterly usage reviews trigger a tier conversation if usage consistently runs above plan.