Which Rebate Structures Aurgus Is Built For
Last updated: November 11, 2026
Aurgus is built for single-entity wholesale distributors running 3–20 active vendor rebate programs, where the gap is at the accrual estimation stage and the constraint is audit documentation. It is not built for multi-entity intercompany structures or vendor rebate program management. This page is a fit filter, not a sales pitch.
The ERP rebate gap assessment and the diagnostic conversation both ask questions about your program structure. This article answers the upstream question: before you do either, here is a program structure map — the configurations where Aurgus was designed to close a real gap, and the configurations where it probably isn’t the right tool.
Most software vendors don’t publish this. We do, because a prospect who self-selects in is a better client than one we talked into it. If your situation doesn’t fit, the right answer is to say so now rather than after the diagnostic conversation. This page is a fit filter, not a sales pitch.
Built for: single-entity distributors with multiple active vendor rebate programs
The core use case is a wholesale distributor running 3–20 active vendor rebate programs simultaneously, where each program has distinct terms — volume thresholds, applicable rate tiers, effective date windows — and where the accrual methodology must reconcile each program independently at period-end.
At three programs, manual spreadsheet management is inconvenient. At ten, it is a documentation gap waiting to surface in an audit. The gap is structural: when program terms change mid-period, the prior estimate’s basis is overwritten. When the settlement arrives months later, there is nothing to reconcile against except the current number.
Aurgus closes that specific gap: the accrual calculation engine applies program terms independently for each vendor program, generates a dated calculation trace at the time of estimation, and surfaces the settlement variance against the original estimate rather than the current one.
This also fits a CAS partner who manages the rebate accounting close function for a distribution client. The documentation Aurgus produces — calculation traces, program-term snapshots at calculation date, settlement reconciliation records — is what a CAS partner delivers to the client’s audit. The methodology page describes how that fits.
Built for: programs where the accrual gap is at the estimation stage, not the settlement stage
Aurgus addresses the gap between period-end accrual estimate and final vendor settlement. It does that by governing the estimation methodology: the program terms in effect at calculation date, the volume assumption used, the rate tier applied, and the source data the estimate drew from.
If the gap in your environment is primarily at settlement — the vendor is paying wrong amounts, program terms are disputed, there are discrepancies between what you invoiced and what the vendor calculates — that is a vendor management problem, not an accrual governance problem. Aurgus is not the right tool for that.
The specific signal that you have the right problem: your team generally knows what the settlement will be when it arrives, and the amount is usually close to what you expected — but you cannot document how you calculated the accrual that preceded it. The settlement isn’t the surprise; the missing calculation trace is the gap.
Built for: environments where audit documentation is the constraint, not system access
Aurgus produces documentation. The tool’s core output is a defensible audit trail for each accrual calculation — the input assumptions, the program conditions applied, the resulting estimate, and the settlement variance when payment arrives. If you already have that documentation for every accrual entry, the gap Aurgus closes may not exist in your environment.
The diagnostic question is specific: does your existing system capture the methodology, or only the transaction?
Many ERP systems capture the transaction — the journal entry, the payment receipt, the settled amount — but not the methodology behind the accrual: the volume assumption used, the rate tier applied at estimation time, whether that tier was superseded by a mid-period program amendment. The ERP records what happened; it does not record why the accrual was the number it was.
If your ERP generates methodology documentation automatically — if the input assumptions, the applied rate tier, and the settlement variance are recorded as ledger attributes at the time of entry — then Aurgus is not closing a gap that exists in your environment. If the constraint is that your system captures transactions but not methodology, that is precisely what Aurgus addresses.
Not built for (yet): multi-entity intercompany rebate structures
Complex intercompany rebate arrangements across multiple legal entities are outside the current scope. This includes situations where the rebate program spans the relationship between affiliated entities and the accounting must reflect the intercompany allocation.
The design target is the single-entity distributor or manufacturer running multiple vendor rebate programs. If your organization has intercompany rebate structures requiring consolidated accounting across separate legal entities, the current tool does not cover that configuration.
Not built for: rebate program management
Aurgus is an accounting governance tool. It is not a vendor rebate management platform, and the distinction matters.
Rebate program management — optimizing program terms, managing vendor relationships, tracking performance against targets for negotiation — is an upstream activity. It happens before the accounting function engages with the numbers. The tools in that category are built for sales and procurement teams, not accounting teams.
Aurgus starts where those tools stop: at period-end, when program terms are fixed, purchases are recorded, and the accounting team needs to calculate and document what the accrual should be. If the problem you’re solving is upstream — program terms, vendor relationships, performance modeling — that is a different category.
The fit test
Before the diagnostic conversation, four questions will tell you whether the conversation is worth having.
1. Does your organization run three or more active vendor rebate programs simultaneously? If you have one or two programs, manual documentation may be sufficient. The structural documentation gap that Aurgus closes emerges from program volume — the moment when programs can no longer be reliably tracked individually without a system designed for it.
2. At period-end, is the accrual estimate built from program terms, or derived from prior-period settlements? If your team builds the accrual estimate by applying current program terms to current-period volume, the methodology is in place — the question is whether it’s documented. If the estimate is built by looking at what settled last quarter and adjusting for perceived volume differences, the methodology gap is upstream of the documentation gap.
3. If an auditor asked for the calculation trace behind last quarter’s rebate accrual, could you produce it from documented records without reconstruction? This is the governing question. “Reconstruction” means assembling the rationale after the fact, from memory and reverse-engineered spreadsheet formulas. “Documented records” means the input assumptions, the rate tier applied, and the program terms in effect were captured at the time of calculation. If the honest answer involves reconstruction, the documentation gap is real.
4. Is your operation a single legal entity — or a CAS engagement for a client that is? Multi-entity intercompany structures are out of current scope, as described above.
If yes to questions 1 and 4, and the honest answer to question 3 is that reconstruction would be required — the diagnostic conversation is worth having. If yes to 1 and 4, and your answer to question 3 is that the documentation exists and is defensible without reconstruction — the gap Aurgus closes may not be present in your environment.
Where to go from here
If the fit test points toward a conversation, the ERP rebate gap assessment is the right first step — it surfaces your specific process gaps before the diagnostic call and gives you something concrete to bring.
If you want to understand what the diagnostic covers before deciding, the evaluation guide walks through the full self-assessment process.
What happens after you reply — what the conversation covers, what you leave with regardless of outcome — is at /answers/what-happens-after-you-reply/.
Pricing is at /pricing/.
For a CAS partner positioning framework — how to present this to a distribution client — see How to Position Governed Rebate Accounting to a Distribution Client.
For a full description of what onboarding looks like, see What the First 90 Days With Aurgus Looks Like.