# Accounting Suite: from first period to close

> Learn Accounting through one Acme project: budget, purchase, cash, assets, payroll and month-end close.

_Updated: 2026-10-07_

Accounting Suite connects purchasing, obligations, payments and accounting close. The team works with one company context, effective authority and linked documents on [Railbase Core](/en/learn). The Suite is a Product; the blocks in the illustration are capabilities inside it, not separate subscriptions.

## One case throughout the course

[Acme Workshops](/en/learn/core-company-setup#one-case-throughout-the-course) starts with $20,000 in the bank, buys a $6,000 machine and delivers a $9,000 customer project. Its $10,000 spending plan also includes $2,000 payroll and $2,000 reserve. Each lesson continues the same company, records and evidence. The simplified training documents use zero tax; real company treatment requires its applicable configuration.

Complete the Core foundation first. The operator installs the available Accounting Product; company roles and assigned decision authority determine each person's work. These articles describe a fictional case to prepare in a training company, not records automatically created in the public demo. Approval-only participants use their assigned Core dossiers, not specialist preparation pages.

## Follow the learning path

| Step | Functional lesson | Saved result |
| --- | --- | --- |
| 1 | [Prepare the first period](/en/learn/accounting-first-period) | Chart, open period and one independently approved opening journal. |
| 2 | [Release a budget](/en/learn/accounting-budget) | Versioned $10,000 plan and a traceable commitment. |
| 3 | [Purchase and receive](/en/learn/accounting-purchase) | Approved supplier, order and evidenced receipt. |
| 4 | [Match and book the invoice](/en/learn/accounting-payables) | $6,000 payable and confirmed source journal. |
| 5 | [Pay and reconcile](/en/learn/accounting-payment) | Settled payable, payment evidence and reviewed bank reconciliation. |
| 6 | [Invoice and collect](/en/learn/accounting-receivables) | $9,000 revenue and two source-linked receipts. |
| 7 | [Capitalise and depreciate](/en/learn/accounting-assets) | One asset, $100 period charge and confirmed GL evidence. |
| 8 | [Prepare payroll](/en/learn/accounting-payroll) | Approved personnel facts, $2,000 payroll and separate settlement. |
| 9 | [Review tax evidence](/en/learn/accounting-tax) | Applicable source treatment, reconciliations and actual filing status. |
| 10 | [Close the month](/en/learn/accounting-close) | Reconciled statements, budget explanation and authorised closed period. |
| 11 | [Migrate an existing business](/en/learn/accounting-migration) | A separately reviewed source cut in an empty training target. |

## Follow a purchase

Start with the request and its evidence. An authorised person decides within the company's policy. The approved order, receipt and supplier invoice stay connected. Accounts Payable records the obligation; General Ledger acknowledges its source journal. Treasury prepares and releases the payment through separate authorised actions. Settlement returns to the obligation and its ledger evidence.

The homepage walkthrough illustrates this route. It creates no business records. In a real company, every action depends on the person's role, object scope and the accepted Product release.

## General Ledger

GL retains the source of each posting. Balanced journals, period close and financial reports share a traceable history. Subledgers request a posting through Core events; the ledger posts the source once and returns its acknowledgement.

## Accounts Payable

AP connects supplier invoices, obligations, approval and settlement. A posted invoice creates a payable. A payment run and its accounting evidence remain linked to that obligation.

## Accounts Receivable

AR connects customer invoices, receivables and receipts. Allocations, credits and refunds retain their relationship to the original customer obligation.

## Treasury

Treasury turns an approved payable run into a draft payment batch. Preparation, approval and release have distinct responsibilities. A completed payment returns evidence to AP for settlement.

## Tax

Tax connects configured tax treatment and calculations to source documents and accounting evidence. The applicable company configuration and accepted release determine the supported scope.

## Fixed Assets

FA follows acquisition, custody, depreciation and disposal. Asset events retain their documents and accounting impact through the ledger.

## People and Payroll

HTR connects employment and payroll work to the company's people and authority context. Approved payroll evidence can feed the ledger. Organisation on the Core remains the shared responsibility structure.

## Procure to Pay

PTP follows a purchase from request through the authorised decision, order, receipt and matched supplier invoice. It connects to AP for the supplier obligation and uses Core authority and documents.

## Budget and Spending

Spending decisions remain related to the relevant budget and their evidence. Budget and spending capability complements purchasing and accounting; the illustrated block belongs to the Accounting Suite.

## Budgeting

Budgeting provides the common budget context for planned work and financial decisions. Accounting and GRC share this capability; the illustration shows one block rather than two copies.

## Connector

Connector connects declared external sources and mappings through the platform. Supported integrations depend on the accepted release and configuration. It is shared by the Suites and is not sold separately.

## Choose the next action

- Read [authority and delegation](/en/learn/authority-and-delegation) before configuring a decision route.
- Read [decisions and evidence](/en/learn/decisions-and-evidence) to understand the linked history.
- Continue to [GRC Suite](/en/learn/grc-suite) for risk, compliance, controls and independent review.
- Check [Product availability](/en/learn/product-availability) and the [company subscription rule](/en/learn/pricing-and-capacity) before starting in [Account](/account).

The accepted Product contract, installed release and company permissions determine usable functionality. The illustration describes the architecture and does not replace Product acceptance.