> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/api.1/use-cases/bookkeeping.md).

# Bookkeeping

Bookkeeping is the foundational process of recording a company's financial transactions. The two central components of this process are payments and journals. They work in tandem to ensure that every financial event is accurately and chronologically captured, forming the basis for a company's financial statements.

### Journals

A journal is the "book of original entry," the very first place a financial transaction is recorded. It provides a detailed, chronological record of all business activities.

* Journal Entries: Each transaction is logged as a journal entry. In a double-entry bookkeeping system, every journal entry has two components: a debit and a credit. The total debits must always equal the total credits, ensuring the books remain balanced.
* Key Information: A journal entry typically includes:
  * The date of the transaction.
  * The accounts affected (e.g., Cash, Accounts Payable, Rent Expense).
  * The debit and credit amounts.
  * A brief description of the transaction.
* Specialized Journals: For efficiency, businesses often use specialized journals for common, repetitive transactions, such as a Sales Journal for credit sales, a Cash Receipts Journal for incoming cash, and a Purchases Journal for purchases on credit.

### Payments

Payments represent the actual movement of money, either in or out of the business. In bookkeeping, payments are the specific events that trigger the creation of a journal entry.

* Outgoing Payments: When a business pays for a purchase, such as paying a supplier invoice, this is a payment. This event is recorded as a journal entry that decreases the Cash account (a credit) and decreases the liability account, such as Accounts Payable (a debit).
* Incoming Payments: When a business receives a payment from a customer, this is also a financial event. The corresponding journal entry would increase the Cash account (a debit) and decrease the Accounts Receivable account (a credit).

#### The Bookkeeping Process

Payments and journals are inseparable in the bookkeeping process. The process generally follows these steps:

1. Identify a Transaction: A financial event occurs, such as a customer payment, a supplier payment, or a cash purchase.
2. Create a Journal Entry: The bookkeeper records the transaction in the appropriate journal. This entry details which accounts are debited and credited.
3. Post to the General Ledger: The information from the journal is then "posted," or summarized, to the general ledger. The general ledger organizes all of the journal entries by account, providing a total balance for each account.
4. Reporting: The balances from the general ledger are then used to create [financial reports](/api.1/use-cases/financial-reporting.md) like the trial balance, income statement, and balance sheet.

In essence, a payment is a specific financial event, while a journal is the system used to formally record that event in a structured, chronological, and balanced manner.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zwapgrid.com/api.1/use-cases/bookkeeping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.