Mapping
One identity surface: every client and every product, matched across every connected tool. What you decide here is what your numbers stand on.
Mapping is where you tell BillRecon who is who and what is what: which vendor customer belongs to which client in your PSA, and which vendor product is the same thing as which PSA billing line. It's the first stop after connecting, because a client only starts producing dollar figures once it's matched, and a product only compares once it's mapped. You decide each one once and BillRecon remembers next month. Open it from Mapping in the sidebar.
Clients, across every tool
Mapping · Clients
Match each of your clients to its vendor account
| Your client | Matched to | Confidence | Status |
|---|---|---|---|
Globex Corp +$1,200.30 | MicrosoftGlobex Global Inc | confirmed | matched |
Acme Inc −$234.56 | MicrosoftAcme Incorporated | 88% nameneeds confirm | to confirm |
TechStart Ltd no drift yet | Microsoftno confident match | no suggestion | needs a pick |
The heart of Mapping is the clients × tools matrix: one row per client, one column per connected tool (or per category, once you have many tools).
- The counters at the top ("14 of 16 clients matched", "12 of 14 SKUs mapped") are your progress. BillRecon only counts drift for clients you've matched, so this tells you how much of your book is covered.
- Each cell is one decision. A check means matched, a question mark means there's a candidate waiting for you, a circle means nothing is linked yet, and a dash means that client isn't on that tool. Category columns aggregate to "N/M" so a pending decision is never hidden.
- The drift column on the right is that client's net drift once it's matched (amber is money to recover, red is an over-charge). The dollar is a door: it opens the client's page.
- Expand a row to decide in place: confirm the suggestion, pick a different match, or mark a tool as not resold to that client. Every suggestion shows its evidence, and everything is reversible.
- Auto-match sweeps every high-confidence suggestion (92% and up) in one click.
- Vendor customers with no PSA client yet wait in their own tray: link one to a client, or exclude one you don't bill (an internal tenant, a test account).
Products and SKUs
Mapping · Products
Map a product once and BillRecon remembers it next month
| Product | Bought / seen as | Billed as (PSA) | Status |
|---|---|---|---|
Microsoft 365 Business Standard seat | PC365-STD99% namehigh confidence | M365-BUSINESS-STD | mapped |
Acronis Cyber Protect seat | BKP-ACRONIS96% namehigh confidence | BKP-ACRONIS | mapped |
Defender for Endpoint P1 seat | DEF-EP-P174% nameneeds confirm | no billing code yet | Confirm |
Below the matrix, SKUs to decide lists every vendor SKU still waiting on a product decision.
- Confirm a suggested mapping when it's right (always reversible), or pick another product by hand.
- Map an unmapped SKU by choosing an existing product or creating a new one (giving it a name and whether it's billed per seat, device, or service).
- Products (every mapped row, browsable, with re-pick verbs) and Contract lines (which PSA agreement line bills each product) are sibling tabs at the top of the page, beside Service plans (what each managed fee includes).
Every client
Need to reach a client that has no drift this month? Clients in the sidebar lists every client in your book, drift or not, with its status and net, each row a door into its page. Clean and flat-fee clients are reachable there even though the Exceptions grid never lists them.
Deciding is reversible, and honesty is the default
Nothing here bills anything. Matching and mapping only decide what's in scope. If you get one wrong, unlink it and pick again. And a vendor product that isn't mapped yet is kept out of your drift number rather than counted with a guessed price, so your headline never inflates on something you haven't confirmed.
Next: Exceptions. For the bigger picture, see the reconciliation workflow.