Custom accounting is for companies whose money events do not fit a package. If you only need tax from sales, an export is often enough. Custom settlement, branches, or wallets usually need your own ledger.
Audience, risk, and how KGSM works
A finance manager whose packaged accounting cannot express settlement or branch rules
A weak ledger means lying management reports and an indefensible audit.
KGSM builds custom only when an export to a package is not enough; vouchers, periods, roles, and logs start on day one.
Custom vs export
KGSM’s test: can the accountant post a standard voucher from the operational system? If yes, we export. If vouchers must carry your rules, we build a ledger. Version one: voucher, trial balance, roles, period close. Multi-year budgets wait.
First ask whether an export to a package is enough. A company bought packaged accounting and posted sales by hand at night; they ran a week behind.
Roles and non-repudiation
Poster and approver are split. Posted vouchers reverse; they are not deleted. Print and void logs exist. A restore is rehearsed on staging. That is the hidden cost of cheap packages.
Deleting vouchers instead of reversing made the trial balance inexplicable. Reverse posted vouchers; do not delete them.
Operations into the ledger
Shop invoices or fund installments must post documents rather than a nightly manual session. Operational ids stay on the voucher. Bank API receipts land on the same ledger.
Split the approver role. Everyone was admin and salaries leaked in a report.
Gateway deposits never became vouchers and bank matching took three days. Keep operational ids on the voucher.
Practice period close before month-end reporting. A company bought packaged accounting and posted sales by hand at night; they ran a week behind.
Deleting vouchers instead of reversing made the trial balance inexplicable. Rehearse a full backup restore once.
Implementation checklist
- First ask whether an export to a package is enough.
- Reverse posted vouchers; do not delete them.
- Split the approver role.
- Keep operational ids on the voucher.
- Practice period close before month-end reporting.
- Rehearse a full backup restore once.
Field scenario 1
A company bought packaged accounting and posted sales by hand at night; they ran a week behind.
First ask whether an export to a package is enough.
Field scenario 2
Deleting vouchers instead of reversing made the trial balance inexplicable.
Reverse posted vouchers; do not delete them.
Field scenario 3
Everyone was admin and salaries leaked in a report.
Split the approver role.
Field scenario 4
Gateway deposits never became vouchers and bank matching took three days.
Keep operational ids on the voucher.
Approximate investment
A custom ledger costs more than an export into a package. If an export is enough we will say so. A first voucher-and-period version is typically tens of millions of tomans or more.
FAQ
Are Iranian packaged ledgers enough?
For many companies, yes, if we can emit a standard voucher. Custom settlement needs custom.
What is version one?
Voucher, period, roles, trial balance, export. Payroll and fixed assets often wait.
Bank connection?
Gateways and cores if samples and test environments exist; estimated separately.
Related KGSM pages
When you apply this on a live team, write it as an operating rule, not a slide: First ask whether an export to a package is enough. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Reverse posted vouchers; do not delete them. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Split the approver role. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Keep operational ids on the voucher. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Practice period close before month-end reporting. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Rehearse a full backup restore once. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A company bought packaged accounting and posted sales by hand at night; they ran a week behind. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Deleting vouchers instead of reversing made the trial balance inexplicable. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Everyone was admin and salaries leaked in a report. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Gateway deposits never became vouchers and bank matching took three days. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A weak ledger means lying management reports and an indefensible audit. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: KGSM builds custom only when an export to a package is not enough; vouchers, periods, roles, and logs start on day one. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A finance manager whose packaged accounting cannot express settlement or branch rules Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A custom ledger costs more than an export into a package. If an export is enough we will say so. A first voucher-and-period version is typically tens of millions of tomans or more. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: First ask whether an export to a package is enough. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Reverse posted vouchers; do not delete them. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Split the approver role. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Keep operational ids on the voucher. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Practice period close before month-end reporting. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Rehearse a full backup restore once. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A company bought packaged accounting and posted sales by hand at night; they ran a week behind. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Deleting vouchers instead of reversing made the trial balance inexplicable. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Everyone was admin and salaries leaked in a report. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: Gateway deposits never became vouchers and bank matching took three days. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A weak ledger means lying management reports and an indefensible audit. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: KGSM builds custom only when an export to a package is not enough; vouchers, periods, roles, and logs start on day one. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A finance manager whose packaged accounting cannot express settlement or branch rules Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: A custom ledger costs more than an export into a package. If an export is enough we will say so. A first voucher-and-period version is typically tens of millions of tomans or more. Then assign an owner and a review date so the rule survives the first busy week.
When you apply this on a live team, write it as an operating rule, not a slide: First ask whether an export to a package is enough. Then assign an owner and a review date so the rule survives the first busy week.