GL account mapping
Which GL accounts Drypowder payments post to, the system journal sequence numbers, and the Spruce screens where the mapping is configured.
This page documents where Drypowder payments land in the Spruce general ledger and where that mapping is configured. Your implementation lead sets these during onboarding; this is where to look if you want to check them. For the concepts behind these entries, see How payments post to the general ledger.
Payment method sequence numbers
Spruce assigns each point-of-sale payment method a system journal sequence number. Drypowder payments post as Bank Cards, sequence 37.
| Sequence | Payment method | Account type |
|---|---|---|
| 35 | Cash | Asset |
| 36 | Checks | Asset |
| 37 | Bank Cards | Asset |
| 38 | Gift Cards | Liability |
| 39 | Coupons | Liability |
| 40 | A/R Credit Payments | Asset |
| 41 | Order Deposits | Liability |
| 42 | C.O.D. Receivables | Asset |
| 43 | Miscellaneous Pay-ins | Income |
| 46 | Charge | Asset |
Where the mapping is configured
Two screens hold the mapping, plus the drawer assignment that determines which branch a payment routes to.
| Screen | Path in Spruce | What it controls |
|---|---|---|
| Payments Mapping | General Ledger, System Journals, Point of Sale Mapping, Payments Mapping | Which GL account each payment method posts to, including Bank Cards at sequence 37 |
| Detail Mapping | General Ledger, Database, Detail Mapping | The card-type-level breakdown, mapping individual bankcard types to their own GL accounts, per branch |
| eCommerce Cash Drawer | Maintenance, Database, Branches, Ecommerce tab | The per-branch drawer that online payments post to |
Branch routing
Both sides of a payment entry route to the branch where the original sale occurred. On the Point of Sale system journal, a per-entry Branch setting determines whether branch-specific accounts are used. When it is on and branch accounts exist, identified by the department code in the GL account number, Spruce uses the branch account in place of the default.
Grouping Drypowder payments
If you want online payments grouped in the ledger, ask your implementation lead to set up a dedicated Bankcard type in Spruce, for example one named DRYPWR, and map it to its own GL account through Detail Mapping.
If you also run Spruce Ecommerce, your Drypowder payments and your Spruce Ecommerce payments share that same dedicated Bankcard type, so a filtered view groups both online payment streams together rather than isolating Drypowder on its own.
Spruce help topics
For the underlying Spruce behavior, these help topics go deeper. Some require a Spruce Support or customer portal login.
- GL Life Cycle of an AR Charge and Payment: how a charge and its payment move through the ledger.
- Point of Sale Mapping, Payments: how each payment method maps to a GL account, including Bank Cards at sequence 37.
- Detail Mapping: mapping individual card types to their own GL accounts, per branch.
- eCommerce Cash Drawer: assigning the per-branch drawer that online payments post to.
- Statement Discounts and the Fast FAQs on understanding statement discounts: how Spruce applies and posts a statement discount.
- Card Processing Reconcile: reconciling bankcard activity against your deposits.
Related
- How payments post to the general ledger — What the entry means.
- Verify how a payment posted — Find it in your ledger.