Financial Accounting System: How to Organize General Accounts, Receivables, Payables, and Reconciliations?
📅 10/11/2026
A company that handles both cash and credit sales needs to make careful decisions about general accounts, receivables, payables, and reconciliations. Choosing a financial accounting system does not begin with a long list of features; it begins with understanding which processes must be controlled and which results should be measured. This guide explains practical steps for testing and implementation in a Saudi business environment, with examples that help distinguish essential functions from unnecessary extras.
What Are General Accounts, Receivables, Payables, and Reconciliations?
The idea is to turn daily procedures into data that can be reviewed and linked to documents and reports. Implementation differs by business activity, but the principle remains the same: every transaction has a responsible person, a reference, and a traceable result. This helps a company that handles cash and credit sales rely less on memory and disconnected files.
When evaluating a financial accounting system, ask how it handles errors and unusual cases, not just ideal transactions. Employees should be able to identify the next step, and managers should be able to understand the impact of any change without manually reconstructing the process.
Which Problems Should You Identify Before Choosing a System?
Start by observing operations over several normal days and one busy day. Document situations that require corrections or additional approval, then classify them by frequency and impact on cash, inventory, or customer service.
• Entering the same document more than once across different programs or files.
• Discovering discrepancies only at the end of a shift or month.
• Lacking a clear reference for changes, cancellations, or approvals.
• Management reports not matching the original invoices and transactions.
• Difficulty transferring responsibility between employees without losing information.
Do not try to solve every problem at once. Choose three recurring processes and set a measurable acceptance criterion for each. If completion time or result accuracy does not improve after the trial, the issue may lie in the procedure or training rather than the software.
To explore the scope of business solutions, review https://nezami.pro/services/Accounting-and-point-of-sale-system-ar and then confirm which functions are included in the appropriate plan.
Data to Prepare Before Going Live
• A list of users, roles, and required permissions.
• Customers, suppliers, and products or services, with duplicates removed.
• Accounts and opening balances reconciled against supporting documents.
• Branches or work locations, payment methods, and units of measure.
• Approval rules for discounts, corrections, and returns.
• A list of reports that management actually needs.
Data cleaning is not a cosmetic step: a duplicate product or incorrect balance will flow into reports no matter how good the software interface is. Keep a reference copy of the old data and record who reviewed each dataset before importing it.
1. Journal Entries: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, check the debit and credit accounts, reference, and posting date before posting the entry to the general ledger. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving journal entries, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Recording accrued rent expense and paying it at a later date. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing journal entries in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
2. Chart of Accounts: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, classify accounts into assets, liabilities, equity, revenue, and expenses according to the nature of the business. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving chart of accounts, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Keeping customer receivables separate from sales revenue. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing chart of accounts in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
You can book a practical demonstration of this scenario: https://nezami.pro/#book-demo
3. Accounts Receivable: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, monitor customer balances, due dates, and amounts that have been partially paid. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving accounts receivable, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Matching a customer payment to two outstanding invoices. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing accounts receivable in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
4. Accounts Payable: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, link supplier invoices to purchase orders and payments to prevent duplicate payments. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving accounts payable, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Identifying a supplier invoice that is due next week. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing accounts payable in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
5. Bank Reconciliation: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, compare the bank statement with recorded transactions and check bank fees and pending transfers. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving bank reconciliation, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Finding bank charges that have not yet been recorded in the accounts. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing bank reconciliation in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
You can book a practical demonstration of this scenario: https://nezami.pro/#book-demo
6. Accrued Expenses: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, distinguish between the date a service is received and the date it is paid for, in accordance with the adopted accounting policy. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving accrued expenses, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Recording an expense for a service received this month that will be paid later. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing accrued expenses in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
7. Financial Closing: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, review unposted journal entries and unusual balances before approving the accounting period. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving financial closing, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Correcting a duplicate journal entry before preparing the trial balance. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing financial closing in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
8. Financial Statements: What Should You Test?
In the context of general accounts, receivables, payables, and reconciliations, link the income statement, statement of financial position, and cash flow statement to balances that can be traced back to source records. This matters because an error at this stage may carry over into other steps without appearing immediately. Therefore, identify the required supporting document, the authorized employee, and the result that management should expect to see in the report.
Practical Testing Steps
• Prepare a test case involving financial statements, and define the input data and expected result before starting the test.
• Perform the transaction using a regular employee account, then repeat it with lower permissions to test access restrictions.
• Open the relevant report or balance and make sure you can trace it back to the original document.
• Try a permitted correction or exceptional case, and check whether the user, time, and reason for the change are recorded.
Practical example: Explaining the difference between accounting profit and the cash balance. Do not settle for the first successful case; repeat the test after changing an amount, changing the user, or changing when it is performed. This reveals the gap between a sales demonstration and actual working procedures.
When implementing financial statements in a company that handles both cash and credit sales, write a brief procedure explaining who starts the task, who reviews it, and when it becomes final. If manual intervention is needed, record it explicitly as part of operating time and cost, rather than assuming the system automates everything.
Practical Function Comparison Table
| Area | Acceptance Criterion |
|---|---|
| Journal entries | Execute a journal-entry test case and reconcile the document, balance, and change log. |
| Chart of accounts | Execute a chart-of-accounts test case and reconcile the document, balance, and change log. |
| Accounts receivable | Execute an accounts-receivable test case and reconcile the document, balance, and change log. |
| Accounts payable | Execute an accounts-payable test case and reconcile the document, balance, and change log. |
| Bank reconciliation | Execute a bank-reconciliation test case and reconcile the document, balance, and change log. |
| Accrued expenses | Execute an accrued-expenses test case and reconcile the document, balance, and change log. |
| Financial closing | Execute a financial-closing test case and reconcile the document, balance, and change log. |
Use this table to compare systems, not as a substitute for testing. Mark each criterion as “Passed,” “Needs Adjustment,” or “Unavailable,” and record the name of the employee who ran the test and the date.
How Do You Connect Results to Accounting and Inventory?
The value of a financial accounting system becomes clear when a transaction can be traced from entry through to the final report. Check that a cancellation or correction does not create a duplicate journal entry or an unjustified inventory movement, and that previous periods cannot be changed without appropriate authorization and a clear procedure.
• Test a normal transaction, followed by a change or cancellation.
• Review the effect of the transaction on the relevant account or item balance.
• Compare document totals with report totals for the same period.
• Check posting times and synchronization limits when connectivity is interrupted.
• Document cases requiring approval or manual handling.
If your operations involve purchasing, receiving, and transfers between locations, it may help to review https://nezami.pro/services/Procurement-system-ar while confirming that the service scope suits your business.
How Do You Measure Return and Cost Without Assumptions?
Start with measurable indicators before and after implementation. Do not attribute higher sales or lower expenses to the software alone without a fair comparison that accounts for transaction volume, training, and seasonal changes.
| Indicator | Measurement Method |
|---|---|
| Transaction time | Minutes between starting and saving the transaction |
| Correction rate | Number of corrected transactions ÷ total transactions |
| Discrepancies | Unreconciled amounts during reconciliation |
| Report preparation time | Time needed to produce a report with traceable sources |
| Total cost | Subscription, devices, training, integration, and support |
Compare offers based on total annual cost, not just the monthly subscription fee. Ask about additional users, branches, printers, data migration, and updates, and request an explanation of what happens if you change plans or cancel the service.
Once you have defined your requirements, you can review pricing: https://nezami.pro/#pricing
Permissions and Internal Controls
Where the nature of the business allows it, separate transaction execution from review. Do not give every employee unrestricted permission to delete documents, change prices, or reopen accounting periods. A change log is more useful for explaining discrepancies than relying on the team’s memory.
• Define creation, editing, and approval permissions for each role.
• Record the reason for cancellations or returns when necessary.
• Restrict access to sensitive reports and financial data.
• Have exceptions reviewed periodically by someone other than the person who performed the transaction.
• Test backup and data recovery procedures with the provider.
E-Invoicing and Saudi Regulatory Obligations
If the business is subject to e-invoicing requirements, test the issuance, retention, and correction of the appropriate documents under the requirements applicable to it. A button labeled “Electronic Invoice” does not, by itself, demonstrate compliance, nor are all businesses subject to the same integration deadline.
The official source to consult before publishing or signing a contract is the Zakat, Tax and Customs Authority: https://zatca.gov.sa/ . Check the latest guidance and the scope of Phase Two if it applies to the business, and avoid unsupported claims of official certification.
How Do You Test the System Before Signing a Contract?
1. Select processes representing daily operations and important exceptions.
2. Prepare realistic test data without exposing sensitive information.
3. Ask for the scenario to be demonstrated in front of the employees who will use the system.
4. Reconcile the invoice or document against the report and final balance.
5. Test permissions, cancellations, returns, and period closing.
6. Document execution time, errors, and manual handling steps.
7. Request written details of support, migration, fees, and updates.
You can request a trial before making a final decision at https://nezami.pro/business/register . Keep written test results to help you compare alternatives without relying on first impressions.
Phased Implementation Plan
| Stage | Expected Output |
|---|---|
| Preparation | Clean data and define processes and responsibilities |
| Configuration | Set up users, accounts, and devices |
| Testing | Reconcile documents, reports, and exceptional cases |
| Training | Short employee instructions and escalation procedures |
| Go-live | Monitor discrepancies, indicators, and continuous improvement |
This is an organizational sequence, not a promise of a fixed implementation period. The time required depends on data volume, number of branches, integrations, and team experience. Do not discontinue existing procedures until you have verified the new system’s results and data recovery plan.
Ready to Try the System?
Start your free trial or speak with the sales team to help choose the right solution.
Common Mistakes When Choosing a System
• Buying numerous features that the business does not actually use.
• Comparing prices without accounting for devices, training, and integration.
• Relying on an idealized demo instead of real operational data.
• Migrating unreconciled balances or duplicate items.
• Ignoring exceptional cases such as returns and corrections.
• Failing to assign someone to review reports after implementation.
Frequently Asked Questions
Is a financial accounting system suitable for every business?
No. Suitability depends on transaction volume, business activity, required integrations, and total cost.
Can I start with only a few users?
That depends on the plan terms and scalability, so confirm the fees for adding users and branches.
Do cloud solutions always work without an internet connection?
Not necessarily. Offline functions and synchronization methods vary by product and must be tested.
Are ready-made reports sufficient?
No. Figures should be reconciled with supporting documents, and every transaction should be traceable.
What is the most important test before buying?
Test a transaction involving general accounts, receivables, payables, and reconciliations from entry through reporting, then repeat the test with a change or correction.
Does implementation require training?
Usually, yes. Training clarifies permissions, review procedures, and how to handle unusual cases.
Conclusion
Choosing the right financial accounting system begins with understanding general accounts, receivables, payables, and reconciliations and testing them in practice. Then assess reporting accuracy, permissions, and total cost. Start with the most important processes, and expand implementation once you have confirmed data quality and the team’s ability to handle exceptions.
Once you have defined your essential requirements, you can get started at https://nezami.pro/business/register or request a demonstration suited to your business.
Manage Your Business with Greater Flexibility
Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.


