Frequently Asked Questions

Revya connects trade planning, payment matching and deduction recovery for CPG brands. It checks deductions against supporting documents, helps prepare disputes for invalid charges and follows up with distributors. The same records help your team understand what promotions actually cost.

Revya brings deductions, remittances and supporting files into one workflow. Your team can review exceptions instead of matching every document by hand. Revya also tracks dispute follow-ups; one Obvi slotting claim took 17 follow-ups before payment.

Revya reviews promotional allowances, shortages, slotting fees, freight charges, manufacturer chargebacks (MCBs), early-payment discounts, scan allowances, spoilage and compliance charges. Coverage depends on the distributor and available data. We will confirm your requirements during a demo.

Start by connecting your deductions inbox. Revya works with you to set up distributor portals, backup files, carriers and sales data. Connection methods vary by source. For a KeHE recovery estimate, you can provide KeHE Connect details or upload a K-Solve export.

Setup typically takes about two weeks. Recovery timing depends on the evidence available, the deduction type and the distributor’s response. An identified invalid charge or a submitted dispute is not recovered money; repayment is tracked separately.

Revya compares deductions with promotion terms, invoices, bills of lading and proof of delivery. Differences are flagged for review. When evidence is missing, the deduction stays marked as needing data rather than being treated as a confirmed recovery.

Start with your own deduction records. A recovery estimate identifies charges worth reviewing and the evidence needed to pursue them. Compare that opportunity with the proposed service cost and your team’s current workload. An estimate is not a guarantee of repayment.

Pricing depends on deduction volume and the scope of your recovery and planning needs. Book a demo to discuss your workflow and receive a proposal.

Revya works with deduction notices, remittances, portal backup, invoices, sales data and promotion calendars. This includes UNFI and KeHE records, ERP exports and spreadsheets. We will confirm how your sources connect during onboarding; not every source uses a direct API connection.

Connect your deductions inbox and share the sources your team uses. Revya sets up portal access, backup files and sales data with you, then reviews historical deductions. Setup typically takes about two weeks and two to three hours of your team’s time.

The documents depend on the charge. Common examples include the invoice, bill of lading (BOL), signed proof of delivery (POD), purchase order and promotion agreement. Revya links the available evidence to the deduction and flags what is missing.

The charge must be invalid under the relevant agreement, supported by evidence and filed within the applicable dispute window. A shortage with a signed proof of delivery is different from one with no supporting paperwork. Results vary by claim; no win rate guarantees a particular recovery.

Timing varies by distributor, deduction type, documentation and follow-up requirements. Revya tracks each claim’s status and next action so you can distinguish an open dispute from a confirmed repayment.

Connections are read-only. Revya uses encryption in transit and at rest, access controls and multi-factor authentication. A SOC 2 Type II program is in progress. Ask us for security documentation when evaluating Revya.

Tell us which retailers and distributors you work with and what records are available. We will confirm the supported workflow for those accounts before onboarding.

The recovery estimate flow includes a confidentiality agreement and a data-processing addendum for review before you share deduction records. You can also ask the Revya team for security and data-handling documentation.

Initial setup typically takes two to three hours. After onboarding, reviews and questions typically take under 30 minutes per month, depending on your workflow and the information needed.

Your team can review GL coding and prepare records for export and close. Tell us which accounting system and reporting format you use so we can confirm the required fields and workflow.

Review the evidence and tell the Revya team which deduction needs another look. Your team stays involved in decisions about accepting charges and approving disputes.

Track charges reviewed, claims in dispute and confirmed repayments separately. You can inspect the evidence and follow-up status behind each claim, then compare actual trade spend with your plan.

Email support@revya.ai or contact the Revya team through the channel agreed during onboarding. Include the deduction reference and deadline when a dispute needs urgent attention.

Revya can help compare your calendar with historical deductions and supporting agreements. Missing promotion details are flagged for review so your team can fill in the gaps.

Discuss your brands, accounts and access requirements during the demo. We will confirm how to organize the workspace and reporting for your team.

Share the existing dispute references and statuses during setup. That helps Revya distinguish open claims from new opportunities and avoid duplicate work.

Book a 30-minute demo or request a recovery estimate. For an estimate, review the confidentiality agreement, choose your data source and share deduction records. We will review the findings with you before discussing onboarding.

That depends on your deduction history, the evidence available and distributor decisions. Start with a recovery estimate based on your own records. Identified opportunities are kept separate from confirmed repayments.

An internal process needs to collect documents, validate charges, prepare disputes, follow up and code records for close. Revya brings those steps into a managed workflow and connects the results to trade planning. Compare the scope and cost with the work your team handles today.

Ask the Revya team about a relevant customer reference. You can also read the published Obvi case study on our customer page.