Postkey
A post key names one kind of posting line, such as "customer receivable", "sales revenue" or "input tax", with the side it normally falls on. Documents do not name accounts directly: they produce lines with post keys, and Posting Profile says which account each post key goes to.
What it is for
Post keys are shared by every company. They are the vocabulary of the posting rules.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Post Key | The code | Required. Unique |
| Name | What the line is | Required |
| Account Layer | Which ledger layer the line belongs to: general ledger, customer or vendor | Required. On a customer-layer post key the customer is written on the voucher line; on a vendor-layer post key the vendor |
| DCInd | The usual side, debit or credit | Required |
| Predefined | Delivered with the system | |
| Reverse Postkey | The post key that undoes this one | When a system voucher is reversed, each line takes the reverse post key. A sales posting line set to use the reverse post key looks up the reverse post key's account |
| Posting Category | The module the post key belongs to | Optional |
Two post keys have a fixed meaning in the general ledger: G70 (inter-unit debit) and G71 (inter-unit credit), set on Automatic Transaction.
What it is connected to
- Process Post Key - which post keys each screen produces.
- Posting Profile - which account each post key goes to.
If something looks wrong
- "Postkey already exists" Use another code.
- "Reverse PostKey is not configured for ..." A sales posting line asks for the reverse post key and this post key has none. Fill Reverse Postkey.