Trade-deal pricing, accrual, claims and settlement for Finance & Operations, so the money you promise a customer is approved before it costs anything, frozen into the price, accrued when goods move, and claimed to a credit you can prove.
In a trade business the price on the line is not one number. It is a base, a premium over that base, and deal money the customer will claim back months later. Finance & Operations stores one unit price, models allowances off the price rather than inside it, accrues at invoice rather than at shipment, and references agreements live, so a deal edited in March silently restates an order accepted in January. The gap gets filled the way it always does: a spreadsheet that knows what was promised, a query that checks the caps, and a person who remembers which accruals were already claimed. Deal money is the biggest liability on the balance sheet that the ERP does not actually govern.
Earmark turns deal money into a governed object. A deal is approved by workflow, with segregation of duties enforced, before it can price anything. When an order is accepted the price is built as base plus over-basis plus deal money, grossed into the invoiced price or carried as an allowance, and frozen: later deal edits never restate it. When goods ship or invoice, the accrual posts as a real journal in the deal's currency, against a lifetime cap and thresholds the engine enforces in the same transaction. Claims are governed documents with their own approval, credited to the customer and settled in standard accounts receivable, and every release of money has an identity, an approver and a ledger reference. The same engine runs the vendor side: supplier rebates, supplier-funded programmes as one linked mirror, purchase price build-up, and freight, broker or commission accrued at customer ship.
What it means for you
Built to depend on
Earmark installs as one signed package beside native Trade Allowance Management and Rebate Management without extending, wrapping or reading either, and a build-time conformance test keeps it that way. It uses Finance & Operations for what it already does well, workflow, posting, number sequences, dimensions, currency revaluation and security, and adds only what native does not have. Its functional model has run a commodity trade in daily production for years; the D365 build is a clean re-implementation that corrects the defects the original carried, and it is maintained across every F&O release.
What's included