The financial close, built for the region.

Close management.

The close calendar, checklists and dependencies for every entity, with owners, preparers, reviewers and due dates. Close templates roll forward each period, and a live status board shows the controller and the CFO what is done, late or blocked.

Account reconciliations.

Every balance-sheet account reconciled from a template suited to its type: bank, prepayments, accruals, fixed assets, intercompany, tax. Risk ratings and materiality thresholds set the review each account needs, and low-risk accounts can be certified automatically by rule.

Preparer and reviewer sign-off, attached support, reconciling items with their ageing, and balances that roll forward to the next period.

Transaction matching.

High-volume matching of bank, card, payment-gateway, intercompany and sub-ledger items to the general ledger. Rules match one to one, one to many or many to many, with tolerances by amount and date. What does not match goes to an exception queue with an owner, and matched items feed the reconciliation.

Journal entries.

Manual, recurring, reversing and bulk entries prepared with their support, validated against your rules and approved at the levels your policy sets. Approved entries go back to your ERP through the connection, or as an import file your team posts.

Variance and flux analysis.

Balance-sheet and income-statement movements compared with the prior period and the budget, against thresholds you set. A movement above its threshold needs an explanation, and the explanation stays on the record.

Close automation.

Repetitive close steps scheduled and run by rule: data loads, matching runs, recurring entries and reconciliation roll-forwards. Where your ERP connection supports it, period-end jobs in the ERP are started and their completion checked from the close board.

Intercompany transactions.

Intercompany charges created, approved by both entities and invoiced from one record, in each entity's currency, with ZATCA-compliant tax invoices where a Saudi entity issues them.

Balancing and netting.

Balances matched across entities, mismatches flagged with their source, netting statements prepared and settlement tracked.

Cash application.

Customer receipts matched to open invoices from bank statements and remittance advice, by rules and suggested matches that an accountant confirms. Short payments and unapplied cash go to an exception queue.

Credit management.

Credit limits, customer risk scores, periodic credit reviews and an approval workflow, with customers flagged before an order or invoice takes them over their limit.

Collections.

Collector worklists prioritised by amount, age and risk, reminders in Arabic and English, promises to pay, and collection performance by collector and by customer.

Disputes and deductions.

Customer disputes and deductions logged, routed to the people who resolve them, and tracked to a credit note or a recovery.

Invoice matching exceptions.

Supplier invoices compared with purchase orders and goods receipts from your ERP; price and quantity differences routed for approval before payment.

Supplier statement reconciliation.

Supplier statements reconciled to the ledger, with differences assigned and followed up.

Controls library.

A risk and control matrix for the finance processes, with each control's owner, frequency, evidence and test steps.

Control testing and certification.

Controls performed and tested on schedule, sub-certifications by process owners, and deficiencies tracked to remediation.

Segregation of duties and audit trail.

Roles that separate preparing, reviewing and approving; every action logged; each approved version frozen with its SHA-256 fingerprint.

Close analytics.

Days to close, late tasks, reconciliation backlog, unreconciled balances by age and risk, and matching rates, by entity and over time.

Risk scoring and anomaly detection.

Accounts and entries scored for risk, with unusual journals and balances flagged for review.

IFRS measurements.

Period-end rules for expected credit losses under IFRS 9, revenue on contracts under IFRS 15, leases under IFRS 16, the end-of-service obligation under IAS 19, inventory under IAS 2 and retranslation under IAS 21. Each rule measures what its standard requires, compares it with the balance held and proposes the entry to post in your ERP. See Notes 1 and 2.

ZATCA, VAT and zakat.

The VAT recorded in your ERP reconciled to your e-invoice records and to the VAT return, and the zakat base computed with the evidence behind each component. Companies on GREENLINE ERP also issue ZATCA Phase 2 e-invoices from the sales module.

CMA and Saudi Exchange reporting.

Quarterly, semi-annual and annual statement packs prepared to issuer deadlines: quarterly within 30 days and annual within three months for the Main Market, semi-annual within 45 days for Nomu. Every figure traces to the close behind it, and the path-to-listing tracker shows each step with its owner and evidence. See Note 3.

XBRL for Qawaem and the Saudi Exchange.

Statements tagged to the IFRS-based taxonomies required by Qawaem, the Ministry of Commerce filing platform, and, for listed companies, by the Saudi Exchange (Tadawul).

Connections.

Data arrives from your ERP as standard extracts (trial balance, sub-ledger detail, open items and bank statements) through secure upload or SFTP, or through a direct connection where your ERP version supports one. The connection for your version is confirmed in the scoped workshop.

GREENLINE reads from your ERP and returns only approved entries. It never changes your ERP's source records, and your ERP remains the system of record.

Security.

Sign-in by e-mail code and authenticator app, roles that separate duties, encryption in transit and at rest, and a complete log of every sign-in and change. No certification is claimed until it is issued.