Who raised the credit limit

The customer master decides how much credit exists and where invoices point. May ledgered 21 changes: six touched the limit, four with approvals on file, one held until its approval exists, one pulled down by collections.

RuleLedger every customer master change with who, when, and both values, and route credit limit raises through a named approval before they take effect.

Neverlet a limit raise work before its approval is on file. Credit extended by an edit is exposure nobody priced, found at the write-off.

The master file decides how much credit exists and where invoices go. Changes to it are decisions, so they ledger like decisions.

◆ May changes, by fieldthree kinds, one partition.

Change type	Changes
Credit limit	6
Remit-to printed on invoices	3
Contacts, terms, and other fields	12
Customer master changes	21

The remit-to rows are the quiet ones: change where invoices tell customers to pay and the money follows. The supplier mirror runs the same play on bank details, and both ledgers keep old value, new value, who, and when on every row. Sample values are illustrative, never client data.

◆ The six limit changesfour clean, one held, one lowered.

Credit limit changes	Changes
Raised, approval on file	4
Raised, held for approval	1
Lowered by collections	1
Credit limit changes	6

The held raise does not work until someone signs it; the customer keeps the old limit and the order that wanted the new one waits. The lowering came from the worklist, which is the control running in the other direction: exposure pulled back when chasing stalls.

◆ The owned answerthe versioned dimension, read as a ledger.

dim_customer on the customer star is versioned, so this page is a query over its own history: every change a row pair, every raise joined to its approval, and a limit that moved without one is a nightly exception, not an annual discovery.

Use case

Problem

Credit limits and invoice remit routes get edited in place, approvals live in email, and the exposure a raise created surfaces at the write-off.

What we build

The customer master as a ledgered history: both values on every change, raises gated on named approvals, remit edits verified before an invoice carries them.

What you get

Exposure that is always signed for: a limit file the credit committee can read, remit routes that cannot drift silently, and the who-changed-what answer in one query.

Who approved your last credit limit raise?

We build the gated change ledger that answers by name.

Talk to us

Terms on this page

credit limit: The exposure ceiling a customer can owe.
remit-to: Where your invoice tells the customer to send payment.
held: Changed in the file but inactive until approved.
version history: Old and new values kept with who and when.