Reyuko User Manual

1. Getting started

Installation and first launch

Install Reyuko and open it. The very first launch runs the onboarding wizard; every launch after that only asks for your PIN.

Onboarding, step by step

1. Language — the interface language. You can change it later in Settings → Preferences, and demo data follows this choice.
2. Sign in with Google — recommended. Your Google account is used for licensing and cloud backup. A "Continue without Google" fallback exists, but signing in is the smoother path.
3. Password, then PIN — the password secures the account; the PIN is the short code you type to unlock the app day to day.
4. Country — the single most important choice. It selects the chart of accounts, the tax framework (VAT/GST name and rate, withholding rules), and the default currency for your region.
5. Currency — your base reporting currency. All reports total in this currency even when you record foreign-currency transactions.
6. Business template — pick the industry closest to yours (retail/trading, F&B, professional services, clinic, wholesale/distribution, rental, courses, digital/SaaS, manufacturing). The template pre-configures accounts, product types, and which modules are on.
7. Data mode — Demo loads a full sample company (contacts, products, and six months of transactions) so you can explore risk-free. Blank gives you only the structural setup so you can enter real data.
8. Setup wizard / welcome — a short finish where you can fill in company details.

Unlocking on later launches

When you reopen Reyuko the session is locked. Enter your PIN to continue. If the app sits idle for about five minutes it locks automatically; from the lock screen you can unlock with your PIN or switch to another user.

Demo data vs a blank start

Demo mode is the fastest way to learn — every module is populated and every report balances, so you can click around freely. When you're ready for real data, go to Settings → Delete sample data to clear the demo, or start a fresh company in Blank mode. Blank mode keeps the structural foundation (chart of accounts, taxes, units of measure, fiscal periods) so you're not starting from nothing.

Step-by-step: First-time setup (onboarding), Setup Awal — initial data.

2. Core concepts

A few ideas make the rest of the app easy to follow.

Workspaces

The colored bar at the top of the window switches workspaces, each a self-contained area with its own sidebar:

• Accounting — the main business application (sales, purchasing, inventory, payments, accounting, contacts, products, settings).
• Document — digital documents, internal notes, document numbering, and the transaction trail.
• Email — an optional built-in email client with contacts and calendar sync.
• POS — the cashier/point-of-sale screen.

App levels: Basic, Intermediate, Advanced

Reyuko grows with you. The app level (Settings → App level) controls how much of the app is visible:

• Basic — a simplified cash-in / cash-out / invoice flow for the smallest businesses. There is a simple Cash module instead of the full Sales/Purchase chains.
• Intermediate — unlocks POS and more modules.
• Advanced — the complete Sales → Purchase → Payment → Accounting suite.

On top of the level you can switch optional modules on or off (production/BOM, fixed assets, payroll, consignment, budget, bank reconciliation, deferred revenue). Turning a module off hides it everywhere; turning the level up reveals whole new sections. This keeps the screen uncluttered for simple businesses while letting complex ones use everything.

Double-entry in one minute

Every transaction touches at least two accounts and always balances: total debit equals total credit. You almost never write this by hand — when you save an invoice, bill, delivery, or payment, Reyuko creates the balanced journal for you. Accounts belong to five families: Assets, Liabilities, Equity (balance sheet) and Revenue, Expenses (profit & loss).

Documents, posting, and status

Business documents progress through statuses:

• Draft — saved but not booked; nothing hits your ledger, stock, or receivables.
• Posted — fully booked: it writes to the general ledger, the inventory subledger, and payables/receivables all at once.
• Unposted — it was posted but has been reversed and can be edited again (allowed only while the fiscal period is open).

Document numbers are generated automatically in the format CompanyCode-Prefix-Year-Sequence (for example RYK-INV-2026-00001). Every number is unique, and you manage the prefixes and running counters in the Document control card (Kartu Kendali).

3. Dashboard

The dashboard is your daily landing page. It shows the numbers you check most — cash on hand, receivables, payables, and sales — plus shortcuts to common actions and a feed of recent activity.

The notification bell at the top right collects what needs attention today: invoices coming due, vendor bills coming due, and note reminders. These come from the Calendar, so the bell and the Calendar always agree. Clicking any notification opens the exact document it refers to.

4. Contacts

Contacts are everyone you deal with. There are five kinds, each with its own list in the sidebar:

• Customers — who you sell to.
• Vendors — who you buy from.
• Employees — your staff (used by payroll).
• Departments and Projects — not people, but tags you attach to transactions so you can report and budget by department or project.

Creating and editing a contact

Open the relevant list, click New, and fill in the form. Only the name is required; the contact code is generated automatically. Useful fields include phone and email, a full address with an optional map link (which shows an inline map preview), the tax ID / NPWP, bank account details, a credit limit, a customer group, and a photo. For Indonesian tax, the "has NPWP" and "PPh 23 exempt" options adjust the withholding rate applied to that contact.

To edit later, select the contact and click the edit (pencil) button in the detail header.

Classifications — the control center for a contact type

Every contact type can have classifications — named groups such as "Retail", "Wholesale", or "VIP" for customers. Manage them from the classification button on the contact list. A classification is much more than a label: it drives several behaviors for every contact assigned to it.

A classification lets you configure:

• A discount for that class of customer — with a validity window. You can make it permanent ("forever") or set a start and end date so a promotion applies only during a period. This is discount layer L3 (see Products → Discount hierarchy) and it applies automatically on every sale to those customers.
• Which contact-person (PIC) slots are shown, and what each one is called. You can enable PIC 1, 2, or 3 independently, and rename their labels — for example rename "PIC 1" to "Billing contact" and "PIC 2" to "Site engineer". The tab and print labels follow the names you choose.
• Which tabs appear in the detail panel — you can hide the transaction (sales/purchase), outstanding, or payment tabs for a class that doesn't need them, and show or hide gender and position fields.

Because these settings live on the classification, you set them once and every contact in that class inherits them.

Customer discount (L3), in practice

When you assign a customer to a classification that carries a discount, that discount is applied on top of any product/category discounts on every line you sell to them — you don't re-enter it per invoice. If the classification's discount has a date window, it only applies within those dates. A per-customer discount field is also available on the contact itself when you want an individual rate rather than a class-wide one.

The detail panel and its tabs

Selecting a contact opens a rich detail panel. The header shows a colored avatar, the name and code, and live key figures — for a customer, the outstanding receivable, credit limit, discount, and last transaction date. The tabs below each serve a purpose:

• Detail — identity, contact info, address (with map), and finance/bank details, grouped into tidy sections.
• Contact person — the PIC records (1–3, using the labels you set on the classification), each with its own name, position, phone, email, and photo. Use this to keep the right person to call for billing, delivery, or technical issues.
• Documents — attach digital files to the contact: signed contracts, agreements, ID scans, tax certificates, and so on (up to eight files per document, organized by document type). This keeps every paper related to a customer or vendor in one place, viewable without leaving the contact.
• Notes — internal, rich-text notes tied to the contact. Notes can use note types with ready-made templates, and — importantly — a note can carry a reminder date that then appears on the Calendar and in the notification bell. Use notes to log calls, agreements, credit decisions, or follow-ups you must not forget.
• Finance — the money view for that contact: their Sales/Purchases documents, their Outstanding invoices/bills with aging, and their Payment history. For a vendor these show purchases and payables; for a customer, sales and receivables.

The print button in the header is context-aware: it prints whatever tab you're viewing (the profile, the PIC sheet, or the finance table), which is different from the list-level print in the command bar that prints the whole contact list.

Departments and projects

Departments and projects aren't contacts you sell to — they're dimensions. Tag a transaction or journal with a department or project and it flows into that dimension's ledger and budget, so you can see revenue, cost, and profit per department or per project.

Step-by-step: Contacts (create / edit).

5. Products & services

The catalog holds both physical goods and services, and the way you configure a product decides how it behaves in accounting and inventory.

Product types (12 of them)

A product's nature is set by five main checkboxes — Sold, Stored, Purchased, Service, Consignment — plus sub-options, which combine into one of twelve types:

• Merchandise / Finished Goods / Raw Materials — stocked inventory with COGS.
• Work in Progress — inventory held during production.
• Supplies — bought and expensed as operating cost, not COGS.
• Fixed Assets — equipment recorded as property and depreciated, not sold.
• Consignment Out — your goods placed with an agent; revenue is booked when the agent reports a sale.
• Consignment In — goods you hold for a supplier; off your balance sheet, you earn commission.
• Standard Service / Service In / Subscription / Digital (SaaS) — services, with Service In bought from a third party and Subscription/Digital recognized over time (deferred revenue).

Pick the type that matches how the item is stored on the balance sheet and expensed — it wires up the right accounts automatically.

Categories, groups, and units

• Categories organize products in a tree and can carry their own discount (layer L2) with a validity window. Querying a category includes its child categories.
• Group products bundle several products under a single group SKU. A group can have its own discount (layer L1), and in POS/e-commerce the individual members are hidden until the customer picks the group — like choosing a variant. Groups are a two-level structure; only leaf groups hold members.
• Units are your units of measure (pcs, kg, box, hour). Each product has a base unit.

Cost of goods (COGS)

Stocked products track cost per purchase batch using one of Average, FIFO, LIFO, or FEFO (first-expiry-first-out). Set the method on the product; each sale then draws cost from the appropriate batch and recalculates the remaining balance.

The discount hierarchy

Discounts apply to the line unit price in a fixed order:

1. L1 — a group discount if the product was added through a group, otherwise the product's own discount (these two are mutually exclusive).
2. L2 — the product's category discount, added on top.
3. L3 — the customer classification discount, added last.

Each layer only counts while its date window is active. Because the layers stack (L2 and L3 on top of L1), the final price reflects all applicable discounts automatically.

Stock alerts, tax, images, vendors

Set a minimum stock threshold to get low-stock alerts. Mark a product taxable and pick its tax; with inclusive tax the entered price already contains tax and Reyuko extracts it, otherwise tax is added on top. You can attach several product images and link up to four vendors for reference.

Step-by-step: Product / service, Categories, Group products, Units.

6. Sales

Selling is a chain of documents; each step can copy from the one before it, so you don't re-key data:

Quotation → Sales Order → Delivery Order → Invoice → Sales Return.

• Quotation and Sales Order are documents only — they record intent and don't touch your books.
• Delivery Order ships goods: it reduces inventory and posts the stock movement.
• Invoice bills the customer: it posts revenue, cost of goods sold, tax, and the receivable. One invoice can gather lines from several delivery orders.
• Sales Return reverses an invoice, in full or in part, and returns stock.

Creating a sale

Choose the module, click New, select the customer, and add line items. For each line pick the product/service, quantity, and tax; discounts (L1–L3) are applied automatically from the product, category, and the customer's classification. Set payment terms if the sale is on credit — a scheme with a grace period, an optional down payment, and instalments — then save. The document total shows subtotal, tax, and grand total.

For a full field-by-field walkthrough of the invoice, with every transaction scenario and its journal, see the New invoice guide.

Recurring invoices

Mark an invoice recurring to have Reyuko generate it on a schedule (daily, weekly, monthly, or yearly). You control:

• End condition — run forever, stop on an end date, or stop after N occurrences.
• Advance generation — create the document a set number of days before its due date.
• Auto-post or draft — post immediately on run, or create a draft for review.
• Customer group batch — point the template at a customer group and each run creates one invoice per customer in that group, with duplicate-per-period protection and a batch log.

You can also skip a single occurrence without breaking the schedule. Recurring documents are executed from the Calendar, whose Execute button shows how many are due.

Step-by-step: New invoice, Delivery order, Sales order, Sales quotation, Sales return, Recurring templates.

7. Purchasing

Purchasing mirrors sales:

Shopping Cart → Quotation Request → Purchase Order → Purchase Delivery → Purchase Bill → Purchase Return.

• Cart, Quotation Request, and Purchase Order are documents only.
• Purchase Delivery is the physical goods receipt: it increases stock and posts Inventory against a GRNI (Goods Received Not Invoiced) clearing account.
• Purchase Bill records the vendor's invoice: it clears GRNI and creates the payable. The tab is labelled "Purchase Bill" precisely because the goods were already received at the delivery step.
• Purchase Return reverses a bill and returns stock to the vendor.

Because stock enters at Purchase Delivery, do the delivery before the bill. Purchase Orders can be recurring, with optional locks so a standing order always uses the contract price and/or quantity.

Step-by-step: Shopping cart (purchase request), Quotation request, Purchase order, Purchase delivery (goods receipt), Purchase bill, Purchase return, Recurring templates.

8. Inventory

Inventory keeps stock accurate across every location, combining the movements from sales/purchases with manual actions.

• Stock list — the current balance of each product per location, with low-stock and out-of-stock indicators computed live.
• Stock movements — the complete in/out/sold history that explains every balance.
• Adjustment — manually increase or decrease stock for usage or corrections; requires an account.
• Transfer — move stock between two locations (both are required).
• Stock-take (opname) — load all products at a location, enter the counted quantities, and Reyuko posts an adjustment for the differences.
• Locations — your warehouses and stores; exactly one is the default.
• Consignment (in) — goods received on consignment stay off your balance sheet; when they sell you book the payable to the supplier and your commission income.
• Production / BOM — consume component products (a bill of materials) to build finished goods. The form must balance — the value of inputs must equal the value of outputs — before it can be finalized; otherwise it saves only as a draft.

Step-by-step: Stock list, Stock movements, Stock adjustment, Stock transfer, Stock-take (opname), Locations, Consignment (received), Production (BOM).

9. Payments

The payment module tracks money moving in and out and keeps receivables and payables current.

• Receivables (AR) — open customer invoices; record incoming receipts here.
• Payables (AP) — open vendor bills; record outgoing payments here.
• Cash & bank — your cash and bank accounts and their movements.
• Cheques / giro — post-dated instruments cleared through their own transition accounts, including bounce handling with a penalty.
• Aging — receivables/payables bucketed by how overdue they are, to spot collection problems.
• Payment terms — reusable instalment schemes with grace periods and down payments.

To settle a document, open Receivables or Payables, select the invoice or bill, and record a payment: amount, date, method, and the cash/bank account. An early-payment discount can be applied where configured. Overpayment is rejected, and deleting a payment cleanly reverses its journal (as long as the period is open).

Step-by-step: Receiving a payment (receivable), Paying a bill (payable), Cash & bank, Cheques & giro, Aging, Payment terms.

10. Accounting

This is the deepest chapter. Reyuko does the bookkeeping for you, but understanding the accounting behind it helps you read reports and trust the numbers. The worked examples below use small round amounts for clarity.

The accounting equation and normal balances

All of double-entry rests on one identity that must always hold:

Assets = Liabilities + Equity.

Revenue increases equity and expenses decrease it, so the working form is Assets = Liabilities + Equity + (Revenue − Expenses). Each account has a normal balance — the side that increases it:

Every entry has equal debits and credits, so the equation always stays balanced.

Chart of accounts

Accounts use a four-level code, a.bbb.ccc.dddd. Level 1 is fixed by standard practice — 1 Assets, 2 Liabilities, 3 Equity, 4 Revenue, 5 Expenses. Levels 2–3 are editable sub-classifications (for example Assets → Current Assets → Cash & Bank). Level 4 accounts are the real ledger accounts you post to (for example "Bank BCA"). System-locked accounts can't be changed or deleted.

Worked example 1 — a cash sale of merchandise

Sell goods for 1,000 plus 11% VAT, where the goods cost you 600. Reyuko posts two journals from the one invoice.

Recognize the revenue and the tax:

Recognize the cost of the goods sold:

Gross profit on this sale is 1,000 − 600 = 400. If the sale were on credit, the first line would debit Accounts Receivable instead of Cash.

Worked example 2 — collecting a receivable

When the credit customer later pays the 1,110:

No revenue is recorded again — it was already recognized at invoicing. This is why sales and cash receipts are separate steps.

Worked example 3 — a purchase, from receipt to payment

Buy inventory for 800 plus 11% VAT. Stock physically arrives at Purchase Delivery, before the vendor's invoice:

When the Purchase Bill arrives, it clears GRNI and records the payable and the recoverable input tax:

Paying the vendor later:

The GRNI account nets to zero once goods received and invoice received match — a built-in check that nothing is received but unbilled, or billed but not received.

Worked example 4 — depreciation

An asset costs 12,000 with a 4-year life (straight-line): 12,000 ÷ 48 months = 250 per month. Each month at closing:

The asset stays on the books at cost; accumulated depreciation reduces its net carrying value over time.

Worked example 5 — deferred revenue (a subscription)

A customer prepays 1,200 for a 12-month subscription. Cash received now is a liability (you owe the service), not revenue yet:

Each month you recognize 1/12 as earned:

Reyuko runs this recognition automatically at period close for subscription and digital products.

Journals and the general ledger

Most journals are posted automatically from documents, as above. You can also write a general journal by hand for entries that have no source document (accruals, corrections, opening balances) — debit must equal credit, and the period must be open. The general ledger lists each account's opening balance, its movements, and its ending balance:

• Opening balance — for debit-normal accounts (Assets, Expenses) it is Σdebit − Σcredit up to the start of the range; for credit-normal accounts (Liabilities, Equity, Revenue) it is Σcredit − Σdebit.
• Ending balance = opening balance + net movement within the range.
• Balance-sheet accounts (1–3) carry balances forward; profit-and-loss accounts (4–5) are closed to equity at year-end.

A trial balance lists every account's debit or credit balance; because every entry balanced, total debits equal total credits — the first check that the books are internally consistent.

Fixed assets and depreciation

Register assets, group them into asset categories, and run depreciation from the depreciation table (straight-line, declining balance, sum-of-years-digits, and others). Depreciation posts monthly at closing over the useful life, using the journal in example 4.

Budgets, reports, and reconciliation

Set a budget per account per period and compare it with the actuals pulled from the ledger; the variance report shows the difference in amount and percentage. Reporting produces the three core statements — the Balance Sheet (Assets = Liabilities + Equity at a point in time), the Profit & Loss (Revenue − Expenses over a period), and the Cash Flow. Bank reconciliation imports a statement and matches it against your ledger so book and bank agree.

Fiscal periods and closing

Every transaction belongs to a fiscal period. Closing a period locks it against edits and runs the period-end engines: foreign-currency revaluation of open balances, deferred-revenue recognition (example 5), accruals, and their reversing entries in the next period. At year-end the revenue and expense accounts are closed into retained earnings. To change a closed period you must reopen it.

Step-by-step: General journal, General ledger, Chart of accounts, Currency, Tax, Fixed assets, Depreciation, Budget, Reporting, Bank reconciliation, Fiscal periods & closing, Currency revaluation, Payroll — salary and its taxes, Tax payment, Year-end closing & corporate income tax, Withholding tax (PPh), Impairment & provisions (asset write-downs).

11. Tax

Tax follows the country you chose at onboarding, so the labels and rates already match your jurisdiction.

• VAT / GST — output tax on sales and input tax on purchases. The name (VAT, GST, PPN…) and rate come from your locale. In Indonesia the standard PPN rate is 11%; 12% applies only to luxury goods.
• Withholding tax (e.g. PPh 23) — deducted at the point of payment for applicable vendor services; the contact's NPWP status can change the rate.
• Final tax and corporate income tax — available where your business entity and scheme require them.

Your company tax profile (Settings) is the master switch: it records whether you're VAT/GST-registered (whether you charge VAT), whether you withhold, your business entity type, and your income-tax scheme. These choices hide or reveal the relevant tax options throughout the app. Behind the scenes, each tax is linked to a real input/output ledger account so every posting lands correctly.

How VAT flows

VAT is not your income or your expense — you collect it on sales (output) and pay it on purchases (input), and remit the difference. Selling 1,000 at 11% credits VAT Output 110 (a liability); buying 800 at 11% debits VAT Input 88 (an asset). At the tax period you net them: 110 − 88 = 22 payable to the tax office. Reyuko keeps the running output and input balances so the amount to remit is always visible.

Withholding (PPh 23) example

When you pay a vendor for a taxable service of 1,000 and must withhold 2% PPh 23, the vendor receives the net and you owe the 20 to the tax office:

The contact's NPWP status can raise the rate (for example to 4% without an NPWP).

Step-by-step: Tax, Tax payment, Withholding tax (PPh), Year-end closing & corporate income tax.

12. Point of Sale (POS)

POS is the cashier workspace, built for fast over-the-counter sales. Switch to it from the workspace bar; it's available from the Intermediate app level up.

Opening a shift

A shift frames each cashier session. Open one at the start, recording the opening cash float and the location the shift sells from; every sale you ring up belongs to that shift, and at the end you close it and get a shift report that totals sales by payment method and reconciles the cash drawer. This is how you hand over the till between cashiers and catch discrepancies. The shift's location matters beyond reporting: it drives the on-hand stock badge shown on each product card and is the location a sale deducts stock from — so two cashiers selling from different warehouses each see and draw down their own stock.

Ringing up a sale

Browse the catalog (search or by category) and tap items into the cart; adjust quantity and any line discount. Group products show their members after you pick the group. When ready, take payment: choose the method (cash, card/transfer, or split across several), enter the amount tendered, and POS shows the change. Print or skip the receipt, and the cart clears for the next customer.

Cash sale vs Pay Later

This is the key accounting point: a normal POS sale is a cash receipt — money received now — not an open receivable. It posts, for a taxable sale:

If instead you choose Pay Later, the sale creates a receivable for that customer (Dr Accounts Receivable) so it can be settled later in Payments — use it for trusted regulars. At the Basic app level, POS can be simplified to skip the receivable and inventory legs for the fastest possible flow.

Held orders

Held orders let you park a cart mid-transaction — a customer forgot something, or you're serving another — and resume it later without losing the lines. Hold as many as you need and pick any of them back up.

13. Calendar & notifications

The calendar view and its markers

The Calendar (Calendar → Event) shows a month or week grid of what's due and what to remember. Each item has a colored marker so you can scan at a glance:

• Blue — an annual/recurring invoice is due.
• Red — a receivable (customer invoice) reaches its due date.
• Green — a payable (vendor bill) reaches its due date.
• Yellow — an annual goods receipt is due.
• Note reminders appear on the date you set them.

Click a date to see its items in a popup; if there are many, it expands to a full list. Every item links to the document behind it.

Executing recurring transactions

The Calendar is the hub for recurring documents. Templates you marked recurring (invoices, purchase orders, consignments) don't post themselves — they wait here. The Execute button carries a count badge of templates that are due (their next run is on or before today, within the advance-generation window). Open it to run the due ones — each creates a real document (posted or as a draft, per the template) — or skip an occurrence without breaking the schedule. Batch invoice templates fan out one document per customer in the group.

Asset calendar

A separate asset calendar (Calendar → Asset) tracks the booking and usage of assets — rooms, vehicles, equipment. It shows which asset is reserved on which dates, populated from the operational (start/end) dates on service lines (see the invoice guide). Use it to avoid double-booking a shared resource.

The notification bell

The notification bell in the top bar mirrors today's due calendar items — invoices and bills due, reminders — and links straight to each source document. Clicking a notification marks it read and opens the document. It's the quick daily check without leaving your current screen.

14. Document workspace

Switch to the Document workspace from the colored bar at the top. This is the paperless-filing and institutional-memory side of Reyuko, kept separate from day-to-day accounting entry. It has four areas: Documents, Notes, the Document control card, and the Transaction Trail.

Documents

Store any digital file as a document record — signed contracts, supplier purchase orders, delivery receipts, ID or NPWP scans, tax invoices, warranty cards. Each record holds up to eight attachments (Office, PDF, and JPG files preview inside the app), a unique document number, a document type (category), a date, a mandatory contact, an optional project or department tag, and a description.

Why it helps: you get one searchable, paperless archive keyed to the contact and the type of document, so the signed contract for a vendor is a click away instead of buried in someone's email. Because a document can be referenced from sales and purchase forms, you attach the source paperwork to the very transaction it supports — your records become audit-ready and you stop hunting through shared drives.

Notes

Notes are rich-text internal notes tied to a contact (and optionally to a transaction or document). Choose a note type to auto-fill a ready-made template, and give a note a reminder date — it then appears on the Calendar and in the notification bell.

Why it helps: this is your institutional memory. Log a phone call, a price agreement, a credit decision, or a "chase this payment on Friday" follow-up, all attached to the right customer. The reminder date means commitments and follow-ups don't slip through the cracks.

Document control card (Kartu Kendali)

A single dashboard of every module's numbering: the prefix, the running number, the current year, and the last few documents issued for each module. Edit a prefix inline, adjust the next number, or reset the counter for a new year.

Why it helps: consistent, professional document numbers across the whole business, controlled from one place. Set your INV, GR, and PO prefixes once, roll the counters over every January, and never guess what the next number should be.

Transaction Trail

Search for any document and see its whole chain: on the sales side, quotation → order → delivery → invoice → payment; on the purchasing side, cart → purchase order → delivery → bill → payment. Each node shows its status, and for invoices and bills it shows how much is paid, partial, or still outstanding.

Why it helps: it's the fastest answer to "what actually happened with this order?" Trace a sale from quote to cash in one screen instead of opening five, confirm what has been delivered, invoiced, and collected, and answer a customer's or an auditor's question on the spot.

15. Email

Reyuko includes an optional built-in email client as its own workspace, so your business correspondence lives right next to your invoices and contacts. It is entirely optional — if you never connect a mailbox, you can ignore this workspace — and your email data stays local to the app.

Mail

Connect a mailbox (a setup assistant walks you through a custom-domain mailbox) and you get a normal client: folders, an inbox, reading, and composing with attachments. When you compose, the recipient box autocompletes from your Reyuko contacts, so emailing a customer is a couple of keystrokes rather than copying an address from somewhere else.

Contacts (CardDAV)

The Contacts tab syncs your address book over CardDAV, keeping the people you email and the contacts in your business in step across your devices.

Calendar (CalDAV)

The Calendar tab syncs a calendar over CalDAV, so appointments and due dates line up with the reminders Reyuko already raises on its own Calendar.

Why it helps productivity: there's no context-switching between an accounting app and a separate mail app — you can read a customer's message while seeing their record and outstanding invoices in the same window. A mailbox on your own domain looks professional to customers, and CardDAV/CalDAV keep your contacts and calendar consistent between your phone and your computer. Because email is built in, that's one less tool — and one less subscription — to juggle. (Sending an invoice by email straight from the document is planned; for now, attach the PDF from the invoice's print view.)

16. Settings

Company profile

Your legal name, address, and logo, plus the bank accounts printed on invoices. The logo uploads directly and shows on printed documents; each bank account records the bank name, account number, holder, and branch and links to a ledger cash/bank account (see the Cash & bank guide). This is the identity that appears across all your printouts.

Users & subscription

Add the people who use Reyuko and give each one of the seven preset roles (owner, accountant, sales, purchase, warehouse, cashier, read-only). Each role is a permission matrix across the modules with three levels — full, read, or none — so a cashier can use POS but not touch accounting settings, and a read-only auditor can see everything but change nothing. Users unlock the app with a PIN; the first user is the owner. The offline plan has a user quota shown on this tab.

Accounting settings

The default accounts and posting rules the modules use — which accounts sales, purchases, tax, and payments post to. These are seeded correctly by your country and template, so you rarely change them; when you add a new bank or a special account, this is where you point the modules at it.

Preferences

The interface language, document numbering (prefixes and running counters — the Kartu Kendali, where you set the format Code-Prefix-Year-Number per module), security (auto-lock after idle), dark mode, and design settings. Language and dark mode preview live; save to keep them.

Initial setup

A guided wizard for entering your real starting data when you go live: opening balances (which you can enter gradually, with a plug account so it always balances while you work), plus contacts, products, and opening stock — often imported from spreadsheet templates. This is the bridge from a blank company to a running one.

Fiscal periods and subscription

Fiscal periods defines and closes your accounting periods (see the Fiscal periods guide). Users & Subscription manages user accounts, roles, and your plan — Free (offline), Starter, or Pro (cloud backup, email, AI, multi-user); see the Subscription guide. Multi-currency is included on every plan.

Changing the app level and modules

From Settings you set the app level (Basic / Intermediate / Advanced) and toggle optional modules (production, fixed assets, payroll, consignment, budget, bank reconciliation, deferred revenue). Raising the level or enabling a module reveals its sections across the app; lowering or disabling hides them. Adjust these as your business grows so the interface always shows exactly what you use — start simple, switch things on when you need them.

Step-by-step: Setup Awal — initial data, Subscription & plans.

17. FAQ & troubleshooting

My demo data is in the wrong language. Demo content follows your interface language — Indonesian for Indonesian, English for every other language. Change the language, then re-seed via Settings → Delete sample data and reload the demo.

A document won't post. Confirm that the fiscal period covering its date is open, that the accounts involved are active, and — for a manual journal — that debit equals credit.

Stock looks doubled or missing. Remember stock enters at Purchase Delivery and leaves at Delivery Order/Invoice; the Purchase Bill and plain invoices don't move stock a second time. Re-posting a document deletes and rewrites its movements rather than adding new ones.

I renamed a PIC but the tab still shows "PIC 1". PIC labels come from the classification, not the contact. Edit the classification's PIC aliases, and make sure the contact is assigned to that classification.

A customer's discount isn't being applied. Check that the customer is in a classification that carries a discount and that the discount's date window is active (or set it to "forever"). Product and category discounts (L1/L2) also have their own windows.

I can't edit a posted or locked item. Posted-final documents and locked fiscal periods are read-only by design. Unpost the document (if allowed) or reopen the period first.

How do I remove sample data? Settings → Delete sample data. This also clears the demo taxes and contacts tied to the sample set.

For anything not covered here, use the search box at the top of this manual to find the relevant section.

Step-by-step guides

The chapters above are overviews. These guides are the detailed, field-by-field walkthroughs of the key forms, each with the accounting behind it — read the relevant one when you're about to fill in a document for real. More guides are added over time.

• First-time setup (onboarding) — see below.
• Setup Awal (initial data) — see below.
• Subscription & plans — see below.
• Cash workspace (Basic level) — see below.
• New invoice — see below.
• Delivery order — see below.
• Sales order — see below.
• Sales quotation — see below.
• Sales return — see below.
• Recurring templates (sales & purchase) — see below.
• Purchase: shopping cart, quotation request, purchase order, purchase delivery, purchase bill, purchase return — see below.
• Payment: receiving a payment, paying a bill, cash & bank, cheques & giro, aging, payment terms — see below.
• Inventory: stock list, stock movements, adjustment, transfer, stock-take, locations, consignment, production, asset groups — see below.
• Accounting: general journal, general ledger, chart of accounts, currency, tax, fixed assets, depreciation, budget, reporting, bank reconciliation, fiscal periods — see below.
• Accounting (period-end & tax): currency revaluation, payroll, tax payment, withholding tax (PPh), impairment & provisions, year-end closing & corporate income tax — see below.
• Master data: product / service, contacts, categories, group products, units — see below.

Guide: First-time setup (onboarding)

The first time you launch Reyuko you go through a short wizard. You do this once; afterwards you just unlock with your PIN.

1. Language — choose the interface language. (This is the one place language is set during onboarding; change it later in Settings → Preferences.)
2. Account — Continue with Google — Reyuko asks for a Google account on every plan; it is the licence/identity layer. Sign in once. Your business data still lives offline on this computer — the account is only used to verify your licence periodically.
3. Password — set an account password. You'll be asked for it about once a month (and when moving to a new device).
4. PIN — set a 6-digit PIN. This is your daily unlock and reappears whenever the app auto-locks after idle.
5. Country — where the business is based. This sets sensible defaults for currency, language, and the tax configuration (e.g. PPN/GST, withholding).
6. Base currency — the currency every journal entry is recorded in. Choose carefully: it locks once the first transaction is recorded.
7. App level (scale) — how much of the app is visible: Basic (simple cash-in/out + invoicing), Intermediate (adds POS and more), or Advanced (the full Sales → Purchase → Payment → Accounting suite). You can raise it later; the chosen template may set a minimum. See Core concepts.
8. Business template — pick the template closest to your business (Retail, Distribution, Manufacturing, Clinic, Services, Rental, Courses, Digital/SaaS, F&B…). It pre-configures the chart of accounts, product types, and transaction codes so you don't start from an empty sheet.
9. Data mode — Demo fills the app with realistic sample data so you can explore safely, or Blank starts empty for your own real data. You can clear demo data later.
10. Business-data wizard — optionally enter master data now (company profile, locations, contacts, products, opening balances), or skip and add it from each module as you go. This hands off to Setup Awal (next guide), which you can return to any time.
11. Welcome — watch the short tour or jump straight to the dashboard.

After onboarding, daily use only needs your PIN; the password is asked about monthly; and the licence re-checks online periodically. If you stay offline past the grace window, the app keeps your data safe and simply asks you to reconnect to refresh the licence — it never locks you out of your own data.

Guide: Setup Awal — initial data

Setup Awal (Settings → Setup Awal) is a persistent setup hub that walks you through getting your real data in. Unlike onboarding, you can return to it any time and finish it in stages. Each stage carries a badge — Done, Draft, Skipped, or To do — and a progress bar tracks the whole thing. Work it as a checklist (jump to any stage) or as a wizard (step by step). Which stages appear depends on your app level, and each stage's "done" state is detected from your real data, so it stays honest.

The stages, in order:

1. Company profile — business name, address, tax ID, and logo. Marked done once the name is filled.
2. Bank accounts — add your bank/cash accounts (name, number, holder), each linked to a ledger account.
3. Chart of accounts — already configured from the template you chose; review it if you like. This stage is pre-marked done.
4. Products & services — download the XLSX template, fill in your catalog (SKU, name, prices, type), and upload it to import in one pass. Or add items by hand in Products.
5. Fixed assets — same pattern: download the asset template, fill in cost, date, useful life, and method, then upload to import.
6. Contacts — download the contact template, fill in customers, vendors, and employees, then upload to import.
7. Opening balances (Saldo Awal) — enter the balances your books start with, so your first reports are correct:
   • Non-stock balances — cash, bank, receivables, payables, equity, and so on. Reyuko posts a balanced opening journal, using a dedicated Opening Balance Equity account (3-1004) as the balancing side. Save it as a draft and finish later; posting is idempotent, so re-running never doubles it.
   • Opening stock — import starting quantities and values via the stock template so inventory and its value are right from day one.

Tips: you don't have to do it all at once — save drafts and come back. The XLSX round-trip (download → fill → upload) is by far the fastest way to load many products, contacts, or assets. If you started in Demo mode, clear the sample data first so demo records don't mix with your real opening balances.

Guide: Subscription & plans

Reyuko runs fully offline on the Free plan; paid plans add cloud and collaboration features on top. You manage this in Settings → Users & Subscription → Subscription, which shows the three plans side by side.

The plans:

• Free — $0. Everything you need to run the books offline on one computer: Sales, Purchase, Inventory, Accounting, Contacts & Products, Fixed Assets & Depreciation, full Reports & Financial Statements, and POS. (The Users tab enforces a user quota on this plan.)
• Starter — $4.99 / month. Everything in Free, plus Document Management (attach & store files), Integrated Email (send invoices/POs by email), Cloud Backup (daily, 90-day history), and the AI Tax Assistant (country-aware).
• Pro — $9.99 / month. Everything in Starter, plus online real-time multi-user sync (2 users included, +$3/month per extra user), real-time Cloud Backup (1-year history), and API / integrations (Peppol, ZATCA, MTD, and similar e-invoicing/tax gateways).

How to subscribe:

1. Open Settings → Users & Subscription and select the Subscription tab.
2. Compare the three cards; your current plan is marked "Current plan."
3. Click Upgrade on the plan you want. This opens the Reyuko pricing page in your web browser — the purchase is completed on the web, using the Google account you signed in with, not inside the app.
4. Finish checkout in the browser. Your licence refreshes on the app's next online check and the new features unlock automatically.

Good to know:

• Because billing happens on the web, you never enter card details inside Reyuko.
• Downgrades and cancellations are handled on the same web account page.
• Your business data always stays local on your computer. A paid plan adds cloud backup/sync on top — it doesn't move your books off your machine.
• The AI Tax Assistant, Integrated Email (see Email), and Document Management (see Document workspace) are the features that light up the moment you move from Free to Starter.

Guide: Cash workspace (Basic level)

The Cash workspace is the simplified money-in / money-out flow shown at the Basic app level, in place of the full Sales → Purchase → Payment chains. It has four screens.

• Cash In — record money received. Pick the receiving cash or bank account, the date, the amount, and a note. It still posts a balanced journal for you (debit Cash/Bank, credit Income), so your books stay correct even though you never see the accounting.
• Cash Out — the mirror: record money paid, debiting the expense and crediting Cash/Bank.
• Invoice / Receipt — issue a simple sales invoice even at Basic level. Add the customer, items or a description, quantities and prices; totals and tax calculate as you type; save to post, then print the receipt.
• Receivables & Payables — a combined outstanding list: unpaid customer invoices on one side, bills you owe on the other. Record a payment against any line to clear it. It is the Basic-level version of the full Payment workspace.

Raising the app level to Intermediate or Advanced replaces this with the full document chains. See App level and Core concepts.

Guide: Asset groups

Asset groups (Inventory → Asset Groups) define the bookable resources your services are scheduled against — a treatment room, a rental car, a piece of hire equipment. They are the master data behind the asset calendar.

A group is one of two kinds:

• Physical — a set of real units. Each unit can be linked to a fixed asset and carries a status (available, maintenance, retired); booking the service reserves a specific unit.
• Virtual (pooled) — a single resource with a capacity instead of named units, for when any of several interchangeable slots will do.

A service product is bound to an asset group through its calendar/asset options. When that service is sold with operational start and end dates on the line, the booking shows on the Asset Calendar, so the same resource can't be reserved twice for one slot. Note this is separate from the Fixed Asset module, which handles depreciation — asset groups are about scheduling, not depreciation.

Guide: New invoice

Open Sales → Invoice → New. The form has a header (the fields below) and a line-items table.

The header, field by field

Customer. Type in the customer box to look up an existing customer by name or code. As you pick one, the form shows its email, phone, and classification so you can confirm the right party. If the customer doesn't exist yet, click + to add a new one on the spot — a name, plus email and phone — without leaving the invoice. (Add the full record, including the classification discount, later in Contacts.)

Document reference no. Optional — record an external reference such as the customer's own PO number for traceability.

Invoice number. Generated automatically as CompanyCode-INV-Year-Sequence (e.g. RYK-INV-2026-00001). To change the prefix or counter, or to enter numbers manually, go to Settings → Preferences → Document numbering.

Source (Sales Order / Delivery Order). If an SO or DO already exists, search and select it here and the invoice fills its lines automatically; one invoice can pull from several delivery orders. How to create an SO or DO is in the Sales chapter.

Currency. Defaults to your base currency; change it for a foreign-currency sale.

Invoice date. The accounting date the entry posts on. Defaults to today.

Due date. When payment is expected. It drives aging and places a marker on the Calendar. With payment terms it's calculated as invoice date + grace period.

Note. Free text describing what the invoice is for; it appears on the printout.

Department. When the Budget module is enabled, department is mandatory — every transaction must carry one so budget-vs-actual by department is complete. With Budget off it's optional. It flows into the ledger as a reporting dimension.

Project. Optional; tag the invoice to track revenue (and cost) per project.

Line items, column by column

Each row is one thing you're billing. Add a row in one of two ways:

• From the catalog — pick a product or service by SKU or name; its price, unit, tax, and any discounts fill in automatically.
• Custom (manual) line — switch on custom mode to type a one-off line that isn't in your catalog (freight, handling, an ad-hoc charge). You enter the description, quantity, and price yourself; a custom line has no stock movement and no cost of goods.

The columns:

• SKU / Product — the catalog item (empty for a custom line).
• Description — the item name; editable, especially for custom lines.
• Qty — the quantity.
• Unit — the unit of measure. A product can be sold in its base unit or an alternate unit with a conversion ratio, so "1 box = 12 pcs" is handled for you.
• Unit price — defaults to the product's selling price. It is editable only if the product allows price changes ("overwrite price"). Once you edit a price by hand, Reyuko won't silently re-price that line when you later change the customer or the date.
• Discount — the effective discount, filled automatically from the L1–L3 hierarchy (group/product, category, customer classification). You can override it per line.
• Tax — the line's tax (see inclusive/exclusive below).
• Amount — the line total: quantity × price, after discount.

Custom (manual) lines

Use a custom line for anything not in the catalog — delivery charges, a one-off service, a manual adjustment. Because it isn't a stocked product, it never moves inventory or posts cost of goods; it simply adds its amount (and tax, if you set one) to the invoice. Give it a clear description so the printed invoice and the ledger read well.

Selling from stock: location, the Stock list, and availability

Because an invoice moves inventory, the form has stock-aware helpers:

• Location. The header Location is the warehouse the goods leave from; it filters the stock figures below. You can also reveal a per-line Location column (a hidden toggle) to ship individual lines from different warehouses. Location only matters for stock-moving documents (invoices and delivery orders).
• Stock list button. Click Stock list to open a browser of your stocked products. It shows each item's name and SKU, its on-hand quantity (at the chosen location), and its price. Search, tick several at once, and add them all as invoice lines — useful when you're picking what to sell against what you actually have.
• On-hand indicator and shortage warning. Each stocked line shows the current on-hand quantity for its product; if you enter a quantity greater than what's in stock, a shortage warning (⚠) appears so you can catch overselling before posting.

The Stock list only lists products that have stock tracking ("manage stock") turned on and are not services; that setting lives on the product, and the locations themselves are inventory master data.

Start date / End date (operational dates)

These two columns are hidden by default and appear only when a line needs to reserve an asset over a period:

• For a service linked to an asset — a physical unit (a specific room, vehicle, or machine) or a virtual/pooled asset — pick the asset and enter the start and end dates. Reyuko checks availability (it tells you whether the asset is free or already booked for that range) and creates a booking that appears on the Asset calendar for those dates. This is how rentals and appointments block out the resource.
• For a custom or plain service line, you can switch on "operational dates" to record a service period without tying it to a specific asset.

Where it's set: the asset link comes from the service product being connected to an asset group, configured on the product/service under its calendar/asset options; the asset groups themselves are master data. The per-line date toggle lives on the line.

Tax: inclusive or exclusive

With exclusive tax (the default) tax is added on top of the line price. With inclusive tax the price already contains the tax and Reyuko extracts it as gross − gross ÷ (1 + rate). The grand total is identical either way — only where the tax sits differs.

Payment section

• Cash or terms — mark the invoice paid now (cash) or on credit (terms).
• Payment terms — a chosen term sets a down-payment %, an instalment count, and a grace period; selecting it fills the down payment, instalments, and the due date.
• Payment method — cash, transfer, cheque, or other; this sets the cash/bank side of the journal.
• Cash / bank account — when paid now, pick the account that received the money; it is debited.
• Cheque / giro — for the cheque method, enter the cheque number, bank, due date, and owner; on save Reyuko records the cheque and holds the amount in a clearing account until it clears (a bounce posts a penalty).

Header actions, saving, and status

The action bar at the top of the form holds:

• Save — saves the invoice as a draft: it's stored but nothing is booked to the ledger, inventory, or receivables.
• Post — books the invoice: it writes the journal, moves stock, and creates the receivable (the scenarios below). A posted invoice is final.
• Unpost — reverses a posted invoice back to editable, allowed only while the fiscal period is open; it removes the journal, stock, and receivable it created.
• Print — opens the printable invoice.
• Internal Notes — attach an internal note to this invoice (not shown to the customer) for context or follow-up.
• Attach Document — link a digital file (a signed copy, proof of delivery) to the invoice.
• Send email — planned; currently disabled.

The status therefore moves Draft → Posted, with Unposted as the reversible middle state if you need to correct a posted invoice. You can't edit a posted invoice or one in a locked period until you unpost or reopen the period.

Recurring settings on the invoice

If you tick recurring, extra options appear: the schedule (daily/weekly/monthly/yearly), the end condition (ongoing, an end date, or a number of runs), how many days in advance to generate the document, whether to auto-post or leave a draft, and — for a customer group — one invoice per contact in the group. See scenario 7 for what posts.

Transaction scenarios and their journals

Assume a line of 1,000 at 11% VAT with goods that cost 600, unless noted.

Scenario 1 — cash sale, paid now:

No receivable is created; the Calendar shows no due marker.

Scenario 2 — credit sale, NET-30:

A receivable of 1,110 is created; its due date feeds aging and adds a red receivable-due marker on the Calendar. You later record the receipt in Payments → Receivables (Dr Bank / Cr Accounts Receivable), which clears it.

Scenario 3 — down payment + instalments (20% down):

The outstanding 888 is split into the instalment schedule, each instalment with its own due date and aging.

Scenario 4 — invoice from a Delivery Order: the goods already left stock at the DO (Dr COGS / Cr Inventory via a delivery-clearing account), so the invoice does not move stock again — it clears the delivery account and recognizes revenue and the receivable (Dr AR / Cr Sales / Cr VAT Output). This is why stock never doubles.

Scenario 5 — service invoice: no cost of goods and no stock movement — Dr AR/Bank, Cr Service revenue, Cr VAT Output.

Scenario 6 — paid by cheque: revenue lines as in scenario 1, but the debit lands in a cheque-clearing account until the cheque clears; clearing moves it to Bank.

Scenario 7 — recurring / annual invoice: marking it recurring creates a template, not an immediate future posting. Each due period it generates a real invoice (posting as above), shows a blue annual marker on the Calendar, and is run from the Calendar's Execute button. For a subscription product, revenue is deferred: cash/receivable now, Deferred Revenue credited, then recognized to Service revenue each period at closing.

Tax collected or not — the controlling setting

Whether the invoice carries a VAT/Output line depends on your company tax profile (Settings → Company → Tax profile):

• VAT-registered (PKP on): taxable lines add a VAT Output credit (a 2-… liability) that accumulates; at the tax period you remit Output − Input.
• Not registered (PKP off): the VAT option is hidden and no VAT line posts.

If you should be charging tax but see no tax column, check the company tax profile first, then that the product is taxable with a tax assigned.

What it affects

• Ledger — every posted invoice writes the balanced journal for its scenario.
• Payment module — a credit invoice creates a receivable (with schedule and aging); a cash invoice does not.
• Calendar & bell — a due date adds a receivable-due marker; a recurring invoice adds an annual marker and is executed from the Calendar.
• Inventory — stocked products reduce inventory (at the invoice, or already at the delivery order); services don't.

Guide: Delivery order

A Delivery Order (DO) ships goods to the customer and takes them out of stock — before you bill them. It sits between the Sales Order and the Invoice: the DO handles the physical hand-over, the Invoice handles the money. Open Sales → Delivery Order → New.

The header, field by field

Customer. The customer receiving the goods (lookup, same as the invoice).

DO number. Auto-generated (CompanyCode-DO-Year-Sequence); change the prefix/counter in Settings → Preferences → Document numbering.

Source (Sales Order). Search and select the Sales Order to ship against; the DO fills its lines automatically. Creating a Sales Order is covered in the Sales chapter.

Location. The warehouse the goods leave from — required, because the DO reduces stock at that location. A per-line location override is available for split shipments.

DO date and Delivery date. The DO date is the accounting date the stock movement posts on; the delivery date is when the goods physically go out.

Department / Project. Reporting dimensions; department is mandatory when the Budget module is on (see the invoice guide).

Note that a Delivery Order has no payment section, no tax, and no due date — it moves goods, not money.

Line items

Add the stocked products and quantities being shipped. The same Stock list browser and on-hand indicator / shortage warning apply, so you can confirm availability before posting. A DO deals in goods; its posted value is the cost of goods (COGS), not the selling price.

What it posts

Shipping goods that cost 600 posts a single balanced entry that takes them out of stock into a clearing account:

No revenue, receivable, or tax is recognized yet — that happens on the Invoice, which clears GSNI (Dr COGS / Cr GSNI) and does not move stock again. The GSNI account nets to zero once every delivery is invoiced.

Consignment delivery. If the DO is a consignment shipment to an agent (the goods stay yours until the agent sells them), it credits Inventory into a consignment inventory account instead of GSNI — the value stays on your balance sheet, just relocated.

What it affects

• Inventory — stock goes out at the DO (this is the movement that reduces on-hand).
• Ledger — the GSNI/Inventory entry above.
• Payment module — nothing; a DO never creates a receivable.
• Later — the Invoice references this DO, clears GSNI, and recognizes revenue and the receivable.

Status: Draft → Posted, with Unposted as the reversible middle state (which returns the stock) while the period is open.

Guide: Sales order

A Sales Order (SO) confirms what the customer has agreed to buy. It is a document-only step — it does not post to the ledger, inventory, or receivables — that turns an accepted quotation into an order ready to deliver and invoice. Open Sales → Sales Order → New.

The header, field by field

Customer, SO number (auto), Order date, and Delivery date work like the other sales forms. Source (Quotation) lets you pull the lines from an accepted Sales Quotation. Location, Department/Project, Currency, and Note are the same reporting/context fields. Payment terms can be set here and are carried forward to the invoice.

Line items

Add the products and services ordered, with quantity, price, discount (L1–L3), and tax — the same line grid as the invoice. Here they simply record what was agreed; nothing is shipped or billed yet.

What it posts

Nothing. A Sales Order is a document only: no journal, no stock movement, no receivable. Its job is to lock the agreement and feed the next steps.

What it affects

• Ledger / Inventory / Payment — none.
• Downstream — a Delivery Order ships against it and an Invoice bills against it, both copying its lines.

Status: Open → Complete (mark it complete once it has been fully delivered and invoiced).

Guide: Sales quotation

A Sales Quotation is the price offer you send a customer before they commit. Like the Sales Order it is document-only — nothing posts. Open Sales → Quotation → New.

The header, field by field

Customer and Quotation number (auto) work as elsewhere. Valid until is the date the offer expires. Payment terms, Location, Department/Project, Currency, and Note carry the usual meaning and are passed along when the quotation is accepted.

Line items

Add the products and services being quoted, with quantity, price, discount (L1–L3), and tax — the same line grid as the invoice, here used to price the offer.

What it posts

Nothing — a quotation is a document only.

What it affects

• Ledger / Inventory / Payment — none.
• Downstream — an accepted quotation becomes the source of a Sales Order, which in turn feeds the Delivery Order and Invoice.

Status: Open → Complete.

Guide: Sales return

A Sales Return reverses a posted Invoice when a customer sends goods back. It must reference the original invoice — that's what tells Reyuko which amounts and costs to reverse. Open Sales → Sales Return → New.

The header, field by field

Customer, Return number (auto), and Return date as usual. Source (Invoice) is required — pick the invoice being returned. Location is where the goods come back into stock.

Line items

The returned products and quantities default to what was invoiced; you can return partially but never more than was sold.

What it posts

Returning the full 1,000 + 110 VAT invoice (goods cost 600), still unpaid, reverses the invoice:

If the invoice was already paid, there's no receivable to cancel, so the refund amount becomes a customer credit / advance (a liability — you owe the customer) instead of crediting Accounts Receivable.

What it affects

• Inventory — the returned goods come back into stock at the return location.
• Ledger — the reversal above.
• Payment module — the customer's receivable is reduced (or a credit is created if already paid).

Status: Draft → Posted, with Unposted while the period is open.

Guide: Shopping cart (purchase request)

The Shopping Cart is an internal purchase request — the list of things a team wants to buy. It is document-only (no posting) and starts the purchase chain. Open Purchase → Shopping Cart → New.

Fields: the request number (auto), who requested it, the issue and required dates, and the location/department. Lines are just the items and quantities wanted — no vendor or price yet. It posts nothing; its purpose is to feed a Quotation Request or Purchase Order. Status: Open → Complete.

Guide: Quotation request

A Quotation Request asks a vendor for prices before you order. Document-only. Open Purchase → Quotation Request → New.

Fields: the Vendor (required), the quotation number, an optional Source (Cart) to copy items from, and a validity date. You can hide prices on the printed request. Lines are the items to be quoted. It posts nothing. Status: Open → Complete.

Guide: Purchase order

A Purchase Order (PO) is your firm order to a vendor. Document-only — it commits you to buy but doesn't post until goods arrive. Open Purchase → Purchase Order → New.

Fields: the Vendor, PO number, an optional Source (Quotation), the PO and delivery dates, and payment terms carried forward to the bill. A PO can be recurring for standing orders, optionally locking the contract price and/or quantity. It posts nothing. Status: Open → Complete. Next comes the physical receipt.

Guide: Purchase delivery (goods receipt)

Purchase Delivery records the physical arrival of goods and puts them into stock — before the vendor's invoice. Open Purchase → Purchase Delivery → New.

Fields: the Vendor, PD number, Source (PO) to copy lines from, the Location goods arrive at (required — this is where stock increases), and the receipt date. Lines are the goods and quantities received.

What it posts — receiving 100 units at 200 (value 20,000):

Stock goes in here; no payable and no tax yet — those come with the bill, which clears GRNI. Because stock enters at delivery, always do the delivery before the bill.

Affects: Inventory (stock in), Ledger (Inventory/GRNI). Status: Draft → Posted / Unposted.

Guide: Purchase bill

The Purchase Bill records the vendor's invoice: it clears GRNI and creates the payable. The goods were already received at Purchase Delivery, so the bill does not move stock. Open Purchase → Purchase Bill → New.

Fields: the Vendor, bill number, Source (PO / Purchase Delivery), payment terms, an optional down payment, and — where applicable — a withholding (PPh 23) deduction. Lines mirror what was received.

What it posts — a 20,000 bill with 11% VAT (2,200), on credit:

If you pay part now, that portion credits Cash/Bank instead of Accounts Payable; if you withhold PPh 23, that portion credits PPh 23 payable and the vendor receives the net. GRNI nets to zero once received and billed match.

Affects: Ledger (GRNI/VAT/AP), Payment module (a payable is created, with due date and aging). It does not move stock. Status: Draft → Posted / Unposted.

Guide: Purchase return

A Purchase Return sends goods back to the vendor and reverses a Purchase Bill. It must reference the bill. Open Purchase → Purchase Return → New.

Fields: the Vendor, return number, Source (Bill) (required), and the Location the goods leave from. Lines default to the billed quantities; partial returns are allowed.

What it posts — returning the 20,000 + 2,200 VAT bill while still unpaid:

If the bill was already paid, there's no payable to cancel, so the amount becomes a receivable from the vendor (they owe you) instead of debiting Accounts Payable.

Affects: Inventory (stock out), Ledger (reversal), Payment module (payable reduced or a vendor receivable created). Status: Draft → Posted / Unposted.

Guide: Recurring templates

Reyuko can generate documents automatically on a schedule — recurring sales invoices and quotations, and recurring purchase orders, quotation requests, and goods receipts. They live in two menus: Sales → Recurring Sales and Purchase → Recurring Purchase. A template is a saved document (contact + item lines + amounts) plus a schedule; executing it creates a real document from that template.

Creating a template. Fill the item lines like any invoice or PO, then set the schedule:

• Type — Sales: invoice or quotation. Purchase: purchase order, quotation request, or goods receipt (Bill).
• Contact — a single customer/vendor, or (Sales invoice only) a customer group for batch runs (see below).
• Frequency × interval — daily, weekly, monthly, quarterly, or yearly, times an interval (e.g. every 2 weeks = weekly × 2).
• Start date — when the schedule begins.
• End condition — Ongoing (until you pause or delete it), End date (stop after a date), or N occurrences (stop after a count). An occurrence counter tracks how many have run.
• Advance days — generate the document this many days before its due date (e.g. 3 → created on the 28th for a 1st-of-month due date). The Calendar marks the due date, not the generation date.
• Post mode — Draft (create for review, you post it later) or Auto-post (post immediately on execute). Auto-post applies to invoices.

Purchase-only options.

• Delivery mode / lead days — the PO's delivery date is either auto (order date + lead days) or entered manually.
• Lock price (default on) — reuse the contract price from the template; turn off to update prices at execute time.
• Lock quantity (default off) — reuse the template quantity; turn off to edit it in the execute dialog.
• Auto-email — email the document on generation (when a mailbox is connected).

Executing. Templates run from the Calendar — its Execute Recurring button carries a count badge of everything due (active templates whose next run ≤ today + advance days). You can also execute a single template from its row. The execute dialog previews the document and, for invoices, lets you override auto-post for that one run. Each execute advances the occurrence counter and the next-run date; when an end condition is met the template becomes Completed.

Batch by customer group (Sales invoice). If a template targets a customer group instead of one customer, executing it creates one invoice per contact in that group in a single run. A duplicate check skips a contact that already has a document for the period, and partial failures are logged — the batch continues, and you can re-run only the failed ones. The result reads like "N documents (M skipped from T contacts)."

Skip, pause, complete. You can skip a single occurrence without breaking the schedule — the occurrence after it runs normally. You can pause a template (Active → Paused) and resume later, or delete it. A template's status is Active, Paused, or Completed (end condition reached).

Recurring documents vs subscriptions. Recurring templates schedule whole documents on a calendar. Separately, subscription / SaaS products (a product type) drive deferred-revenue recognition — one invoice is issued and its revenue is recognized period by period, not a new document each time. See the Product / service guide.

Guide: Receiving a payment (receivable)

Use Payment → Receivables to record money coming in against a customer invoice. Pick the open invoice, then record the receipt. Open the receivable and click Receive.

Fields: the amount (can't exceed the outstanding — overpayment is rejected), the date, the method (cash/transfer/cheque), and the cash/bank account the money went into.

What it posts — a full receipt of 1,110:

Early-payment discount. If the invoice's payment term offers a discount for paying early and you're within the window, Reyuko computes it: the customer pays less, the shortfall is booked as a discount, and the receivable is fully cleared (Dr Bank net + Dr Discount given / Cr Accounts Receivable full).

Withholding on receipt. If your customer withholds tax (e.g. PPh 23) and pays you the net, the withheld portion is recorded as a prepaid tax (asset) so the receivable still clears in full (Dr Bank net + Dr Prepaid PPh 23 / Cr Accounts Receivable).

Affects: Payment module (the receivable's outstanding drops; when it reaches zero the invoice is paid), Ledger (the entry above). Deleting a receipt cleanly reverses it while the period is open.

Guide: Paying a bill (payable)

Use Payment → Payables to record money going out against a vendor bill. Pick the open bill and record the payment.

What it posts — paying 22,200:

An early-payment discount taken here reduces what you pay and is booked as income/expense reduction. Affects: the payable's outstanding drops; the ledger records the entry.

Guide: Cash & bank

Payment → Cash & Bank lists your cash and bank accounts with their live balances and movements. Its most important use is moving money between your own accounts — for example depositing petty cash into the bank, or drawing cash from the bank — which changes the account balances but is neither income nor expense.

Transferring funds between accounts

Click Fund transfer, choose the from account and the to account (both cash/bank), and the amount.

What it posts — moving 5,000 from petty cash into the bank:

The destination account is debited (it goes up) and the source is credited (it goes down); total cash is unchanged, only its location. Draw the mirror entry to take cash out of the bank.

Direct cash/bank entries

For money that is income or expense — bank fees, interest earned, an admin charge — record a small entry here (or a General Journal): debit or credit the bank account against the relevant expense or income account.

Setting up accounts, and recording bank name and number

Two different things are configured in two places:

• The ledger account money posts to is a Chart-of-Accounts entry. In Accounting → Data Akun, add a level-4 account under Cash & Bank, give it a name (e.g. "Bank BCA" or "Petty cash"), its currency, and mark it as a cash/bank account. This is what appears in the from/to pickers.
• The bank's name, account number, holder, and branch — the details that print on your invoices — are recorded in Settings → Company Profile → Bank Accounts. Add a bank account there, fill the bank name and account number, and link it to its ledger account.

For matching a bank statement line by line, use Bank reconciliation in Accounting.

Guide: Cheques & giro

A cheque isn't cash until it clears, so Reyuko parks it in a transition account and moves it to the bank only when it actually clears. Record cheques from Payment → Cheques / Giro (or by choosing the cheque method on an invoice/bill), entering the cheque number, bank, due date, and owner.

Fields, one by one: the cheque number, the bank it's drawn on, the due date (when it can be cashed), the owner (the party on the cheque), the amount, and the direction — an incoming cheque received from a customer, or an outgoing cheque you issued to a vendor. The direction decides which side of the journals below applies, and the status (in transit → cleared / bounced) tracks where the cheque is.

Incoming cheque (from a customer)

When you receive a customer cheque against their invoice:

When it clears, the money reaches your bank:

If it bounces, the clearing is reversed (the receivable comes back) and an optional penalty can be charged to the customer (Dr Accounts Receivable / Cr penalty income).

Outgoing cheque (to a vendor)

A cheque you issue works the mirror way: issuing it debits Accounts Payable and credits a cheque outstanding liability; when it clears, that liability is debited and Bank is credited. A bounce reverses it, with an optional bank charge (Dr expense / Cr Bank).

Setup

The two transition accounts — a cheque-in-transit asset and a cheque-outstanding liability — are preset in the chart of accounts, along with penalty income/expense accounts. You normally don't touch them; they exist so cheques sit in a clearly-labelled place until they clear.

Guide: Aging

Payment → Aging is a read-only report that buckets your receivables (and payables) by how overdue they are — current, 1–30 days, 31–60, and so on — using each document's due date. It's the fastest way to see who owes you and how late, so you can prioritize collection. Nothing is posted here; it reads the live outstanding balances.

Guide: Payment terms

Payment → Payment Terms is the master list of instalment schemes you reuse on sales and purchase documents. Define a term once here, then just pick it on an invoice, order, or bill.

Fields, one by one:

• Name — how the term shows in pickers (e.g. "NET 30", "30% DP, 3×").
• Type — cash (paid in full now, no due date) or term (on credit).
• Down payment % — the portion due up front (0 for none).
• Instalment count — how many instalments the balance is split into.
• Grace period — days added to the document date to set the due date (document date + grace).
• Early-payment discount % and days — an optional discount if paid within that many days; Reyuko applies it automatically at receipt/payment.

Picking the term on a document fills the down payment, instalments, and due date for you.

Guide: Stock list

Inventory → Stock list shows the live balance of every stocked product, per location. A location tree on the left filters the table (All locations, or one warehouse); the cards on top summarize total SKUs, stock value at cost, and how many items are low or out of stock.

Columns: SKU and Product identify the item; Category groups it; Location is the warehouse; Available is the live on-hand balance (sum of movements in minus out); Reserved shows quantities committed. An item is flagged low when Available falls below its minimum stock and out when it reaches zero — both computed live, not stored. This is a read view; the buttons launch the actions below. It only lists products with stock tracking ("manage stock") on.

Guide: Stock movements

Inventory → Stock movements is the full audit trail behind every balance: each row is one in, out, or sold movement, with its date, product, location, quantity, and the source document (a delivery, invoice, adjustment, or transfer). When a balance looks wrong, this is where you trace exactly what happened. It's read-only.

Guide: Stock adjustment

An Adjustment manually increases or decreases stock outside the normal buy/sell flow — for corrections, usage, spoilage, or found goods. Open Inventory → Adjustment → New.

Fields: the type (surplus / usage / loss / scrapped), the location, the account to book the other side against (required), and lines with a signed quantity (positive to add, negative to remove).

What it posts — writing off 5 units at cost 200 (value 1,000):

A surplus (positive quantity) reverses the direction — Dr Inventory / Cr the chosen account. Scrapped items also mark their serials as expired. Affects: Inventory (stock changes) and the ledger. Status: Draft → Posted.

Guide: Stock transfer

A Transfer moves stock from one location to another. Open Inventory → Transfer → New, choose the from and to locations (they must differ), and list the products and quantities.

A transfer posts no journal — your total inventory value is unchanged, the goods simply relocate. Internally it writes a pair of movements: an out from the source and an in to the destination. Affects: the per-location balances only. Status: Draft → Posted.

Guide: Stock-take (opname)

A Stock-take reconciles your book stock to a physical count. Open Inventory → Stock-take, pick a location, and Reyuko lists every product with its book quantity; you enter the counted (on-hand) quantity, and it shows the difference.

How it records a loss or a gain

On completion it automatically posts a stock Adjustment of type opname for the differences:

• A shortage (counted < book) is a loss — Dr an inventory-loss/shrinkage expense / Cr Inventory — valued at the missing units' cost.
• An overage (counted > book) is a gain — Dr Inventory / Cr an inventory-gain (income) account — valued at unit cost.

You choose the loss/gain account when completing the take.

How the value is calculated (Average / FIFO / LIFO)

The value of a shortage isn't the selling price — it's the cost of the missing units, taken from your purchase batches using the product's COGS method. Suppose a product has two batches: 10 @ 100 (older) then 10 @ 120 (newer), and 15 units leave stock:

The same method values every stock-out — a sale's COGS, an adjustment, or an opname shortage — so your inventory value and cost of sales stay consistent. Set the method on the product (see Products). Run a stock-take periodically to keep inventory honest.

Guide: Locations

Locations are your warehouses and stores — the master list every stock movement is tagged with. Manage them from Inventory → Locations (or the button on the Stock list). Each has a name and optional address; exactly one is the default (used when a document doesn't specify a location), and selecting a new default clears the old one. Inactive locations are hidden from pickers.

Fields, one by one: a name (the warehouse/store), an optional code, optional address details (city, province, postal code, phone, email, map link), a default flag (exactly one location is the default — used when a document doesn't specify one; setting a new default clears the old), and an active flag (deactivate to hide it from pickers without losing its stock history).

Guide: Consignment (received)

Consignment In records goods a supplier leaves with you to sell on their behalf. Because you don't own them, they stay off your balance sheet — recorded only as a memorandum, not as inventory or a payable. Record receipts from Inventory → Consignment, choosing the supplier and the items.

What it posts when you sell — say you sell a consignment item for 150 that the supplier prices at 120 (your commission 30):

There is no cost of goods — the goods were never yours — and (if taxable) a VAT Output line is added. You later settle the payable to the supplier for the goods sold, and return any unsold stock to them.

Guide: Production (BOM)

Production turns component products into finished goods using a bill of materials. Open Inventory → Production → New, list the input components consumed and the output finished goods produced, plus any custom costs (labour, overhead).

Header fields: the production number (auto), the date, the location the materials are drawn from and finished goods land in, an optional document reference and note, and the staff. Line fields each carry a role — input (a component consumed), custom (a labour/overhead cost with no stock), or output (a finished good produced) — plus the product, quantity, and cost.

The bill of materials (BOM / recipe)

A BOM (shown as "Bill of Materials", stored internally as a recipe) is a reusable template of what goes into one finished product: its component materials, any custom costs (labour, overhead), and the finished output. Create it once so you don't re-enter the same structure every time.

Using a BOM in a production run

In a new production run, select the BOM to insert it — the form pre-fills the component lines, custom-cost lines, and the finished-good line from the recipe. Then just scale the quantities to how much you're actually making (or edit lines for a one-off variation) and post. You can also build a run by hand without a BOM, adding inputs and outputs directly.

Work in Progress (WIP), and the journal

Work in Progress is a holding account that represents goods being made — no longer raw material, not yet finished. Everything you put in flows into WIP and everything you take out flows out of WIP, so on a completed run WIP nets to zero. Posting a run writes three kinds of entry.

Example: consume 2 units of RM-A at 100 and 1 of RM-B at 50 (materials 250), add 50 of labour/overhead, to make 1 finished good worth 300.

Issue the raw materials into WIP (stock leaves inventory at its cost):

Add the custom (conversion) costs into WIP — no stock moves:

Move the finished goods out of WIP into finished inventory:

WIP took in 250 + 50 = 300 and released 300, leaving zero. That's why the form's balance (inputs + custom costs − outputs) must be 0 before you can finalize — an unbalanced run saves only as a draft. Choose the WIP account in the posting dialog.

Affects: Inventory (raw materials down, finished goods up) and the ledger. Status: Draft → Posted (only when balanced).

Guide: General journal

The General Journal is where you post an entry by hand — for things without a source document: accruals, corrections, opening balances, reclassifications. Open Accounting → Journal → New.

Fields: the journal number, date, optional department/project dimensions (which flow into the ledger so the entry counts in that dimension's reports and budget), and lines each with an account, a description, and a debit or credit amount. Rules: total debit must equal total credit, and the fiscal period covering the date must be open.

Reversing entries. For accruals (an expense incurred but not yet billed), post the accrual at month-end and mark it to reverse at the start of the next period, so it cancels automatically when the real bill arrives — you don't double-count. The period-end engines use the same reversing mechanism for FX revaluation.

Affects: the ledger only. Status: Draft → Posted / Unposted (unpost while the period is open to edit).

Guide: General ledger

The General Ledger (Buku Besar) shows every account's activity over a date range: its opening balance, each posted movement, and its ending balance — all computed live from the journals. Filter by account and period.

Browsing: list vs tree view

Two ways to pick what you see:

• List mode — choose a single level-4 account and read its ledger.
• Tree view — navigate the account hierarchy (type → group → subgroup → account) and select any node. Pick a level-4 account for just that account, or a higher node (say "Cash & Bank", or the whole "Assets" type) and the ledger aggregates every account below it. This lets you read the ledger of a whole classification without opening each account.

Why accounts 1–3 and 4–5 behave differently

The two families are handled differently, on purpose:

• Balance-sheet accounts (1 Assets, 2 Liabilities, 3 Equity) are permanent — they carry an opening balance cumulative from the company's inception, and that balance rolls forward year to year. Asking for a balance "as of" any date gives the running total up to then.
• Profit-and-loss accounts (4 Revenue, 5 Expenses) are nominal — they are closed to retained earnings at year-end and start each fiscal year at zero. Within a year the ledger shows only that year's movements; there is no cumulative-from-inception opening balance for them.

In both cases mutation = total debit − total credit for the range; the opening/ending logic just differs by family as above.

Guide: Chart of accounts

Accounting → Data Akun is the master list of your accounts. Codes have four levels, a.bbb.ccc.dddd: level 1 is fixed (1 Assets … 5 Expenses), levels 2–3 are editable sub-classifications, and level 4 accounts are the real accounts you post to.

Adding an account

Click New account, choose the level-3 classification it belongs under (for example Assets → Current Assets → Cash & Bank), and fill:

• Name — e.g. "Bank BCA", "Petty cash", "Office supplies expense".
• Code — the 4-digit level-4 number is generated for you under the chosen classification.
• Currency — the account's currency (defaults to base).
• Account kind — a setting that marks the account as standard, cash/bank, or debt/loan. Marking it cash/bank is what makes it appear in the cash/bank and fund-transfer pickers.

Opening balances

When you start with Reyuko mid-life, your accounts already have balances. Enter these opening balances through the Initial setup wizard (Settings → Initial setup) or as an opening General Journal dated before your first transaction — debits and credits must balance, with the difference going to equity. Only balance-sheet accounts (1–3) carry an opening balance; revenue and expense accounts start each year at zero.

Editing, locking, deleting

System-default accounts are locked (checkbox_lock) and can't be changed or deleted. Deleting a level 2–3 account asks you to pick a replacement so its children are reassigned. An account you no longer use can be marked inactive to hide it from pickers without deleting its history.

Guide: Currency

Accounting → Currency lists the currencies you trade in and their exchange rates to your base currency.

Adding a currency and its rate

Click New currency, pick the currency code (USD, SGD…), and set its exchange rate to your base currency. Update the rate whenever it moves; documents use the rate on their date to convert foreign amounts into base-currency debits and credits, and reports always total in base currency.

Default accounts per currency

Each foreign currency maps to its own default accounts — a receivable, a payable, and a bank account (all in that currency) — so a foreign-currency invoice or bill posts its AR/AP and cash to the right places rather than to the base-currency accounts. Set these on the currency; at period end, FX revaluation restates the open foreign balances to the closing rate, booking the difference to an FX gain or loss account. Your base currency is set at onboarding; add others here as needed.

Guide: Tax

Accounting → Tax is the master list of taxes (VAT/GST and withholding). Each tax carries a rate, a type (e.g. VAT vs PPh 23), and — importantly — its linked input (buy) and output (sell) accounts, so that when a document uses the tax the amounts post to real ledger accounts.

Adding a tax, field by field: give it a name (shown on documents, e.g. "VAT 11%"), a type (VAT/GST, or a withholding type such as PPh 23 / PPh 21 / final tax), the rate (percent), whether it is inclusive by default, and its buy (input) and sell (output) accounts. A VAT-type tax uses both accounts (input on purchases, output on sales); a withholding tax typically posts to a single payable account. Once saved, the tax appears in the line-tax picker on documents — subject to the company tax profile, which hides taxes you're not registered for.

Guide: Fixed assets

Accounting → Fixed Assets registers equipment and property you use rather than sell.

Registering an asset

Registering an asset establishes its depreciation basis; it does not double-post the ledger if the asset already arrived through a purchase (that entry already booked it). If you're entering an asset you bought outside the app, post its acquisition once — Dr the fixed-asset account / Cr Cash or Accounts Payable.

Field by field:

• Name and category — the category (below) sets the method, useful life, and accounts, which the asset inherits; you can override per asset.
• Acquisition date — when you got it; depreciation counts from here.
• Cost — the purchase/capitalized cost, the amount to be depreciated.
• Salvage (residual value) — the value you expect at the end of its life; only cost − salvage is depreciated.
• Useful life — how many years (or the table's periods) it depreciates over.
• Depreciation method / table — see the Depreciation guide; usually inherited from the category.
• Quantity, location, serial no., condition, department — descriptive/reporting fields.
• Accounts (fixed-asset, accumulated-depreciation, depreciation-expense) — inherited from the category; override only for a special case.
• Source document — a link to the bill or journal it came from.

Acquired mid-month — the "after the 15th" flag

The after the 15th switch applies a mid-month convention: if you got the asset on or before the 15th, it depreciates a full month in the acquisition month; if you got it after the 15th, tick this and depreciation starts the following month. This keeps the first period fair without pro-rating by day.

Entering an asset that is already partly depreciated

When you migrate to Reyuko, an existing asset already has depreciation behind it. Mark it as a legacy asset and enter the accumulated depreciation to date (its opening accumulated). Reyuko then continues the schedule from where you are — it won't re-depreciate the months already taken, and the remaining depreciable amount (cost − salvage − accumulated) is spread over the life that's left.

Fixed assets vs bookable (service) assets

Don't confuse two different "assets":

• A fixed asset here is depreciable property you own (a vehicle, equipment) — it sits on the balance sheet and is depreciated.
• A bookable asset (an asset group / physical unit, or a virtual/pooled asset) is a schedulable resource for services — a rental car, a treatment room, a piece of hire equipment — reserved through the operational (start/end) dates on a service line and shown on the asset calendar.

The same physical thing can be both: a rental car is a fixed asset for depreciation and a bookable asset for scheduling. A virtual/pooled asset is used when you don't reserve a specific unit — just one of an interchangeable pool.

Asset categories — the setup that drives depreciation

An asset category (Accounting → Asset Categories) is where the accounting is configured: it links the fixed-asset account, the accumulated-depreciation contra-account, and the depreciation-expense account, and it sets the method and useful life (via a depreciation table). Assign each asset to a category and it inherits all of this.

Disposing or selling an asset

Disposal (scrapping) removes the asset — Dr Accumulated Depreciation (and a Loss for any remaining book value) / Cr Fixed Asset (cost). Selling it:

The gain or loss is the difference between the sale price and the asset's remaining book value.

Guide: Depreciation

Accounting → Depreciation spreads an asset's cost over its useful life. The method comes from the depreciation table attached to the asset or its category — straight-line, declining balance, sum-of-years-digits, and others.

The asset stays on the books at cost while accumulated depreciation reduces its net value.

The methods, and when to choose each

Every method is table-driven — a depreciation table holds the per-period rates — so the engine reads the table rather than hard-coding a formula:

Straight-line spreads cost evenly; the accelerated methods expense more in the early years (matching assets that really do lose most value up front).

Method ↔ category ↔ table

You normally don't set the method on each asset. An asset category carries the depreciation table (hence the method and rates), the useful life, and the depreciation accounts; each asset assigned to that category inherits them. So "IT equipment, 4 years, straight-line" is configured once on the category, and every laptop you register under it depreciates the same way. You can still override the table on an individual asset for an exception.

How the schedule is adjusted

The engine keeps the total exact: it depreciates only cost − salvage, honors the mid-month convention (the after-the-15th flag), and absorbs any rounding in the final period so accumulated depreciation lands on exactly cost − salvage — never a cent more or less. Partial first/last years are handled from the acquisition date.

When it's written, and its link to closing

Depreciation isn't continuous — it's posted per period (usually monthly) when you run it from this page. Do it as part of month-end, before you close the period: run depreciation, then close. The run is idempotent per asset and period — running it twice for the same month does nothing the second time — so it's safe to re-run. A closed period can't be depreciated into; reopen it if you need to adjust.

Guide: Budget

Accounting → Budget lets you plan spending and revenue per account and compare against reality.

Setting a budget, field by field: pick the account to budget, the year, and an optional department (so you can budget the same account separately per department). Enter the amount either as a yearly figure or month by month (twelve values). A gatekeeper setting decides what happens when actual exceeds budget: warning (flag it but allow) or block (prevent posting over budget). One budget exists per account, per department, per year.

Reading the variance: the report compares your budget with the actuals pulled live from the ledger — filtered by the same account, period, and department — and shows the difference in amount and percentage. A negative variance on an expense means you overspent; on revenue it means you're under target. Budgets post nothing themselves; they're a planning overlay.

Guide: Reporting

Accounting → Reporting produces the three core financial statements from your ledger: the Balance Sheet (Assets = Liabilities + Equity at a date), the Profit & Loss (Revenue − Expenses over a period), and the Cash Flow. Choose the period and read; every figure traces back to posted journals. Read-only.

Single period vs multi-period compare

Two view modes: single period shows one period's statement, while compare puts several periods side by side — this month vs last, or month by month across the year — so you can read the trend, not just a snapshot. Use compare to spot a cost creeping up or revenue slipping before it shows in a single month.

Ratios and their limits

At the Advanced app level a Ratios tab derives key indicators from the P&L and Balance Sheet, each with a rule-of-thumb benchmark and a status flag:

• Liquidity — current ratio (current assets ÷ current liabilities, benchmark > 2), quick ratio (excluding inventory, > 1), cash ratio (> 0.5). Can you cover short-term obligations?
• Profitability — gross / operating / net margin (> 25% / 15% / 10%), ROA (return on assets, > 5%), ROE (return on equity, > 10%). How much profit per sale and per dollar invested?

Read them with care. These ratios are indicators, not verdicts:

• The benchmarks are generic — a healthy current ratio for a supermarket differs from a software firm; compare against your own industry and history.
• They use book values at a point in time, so a big receipt or payment right before period-end can distort them.
• One-off items (a large one-time sale or write-off) skew margins for that period.
• A ratio tells you where to look, not what's wrong — treat a red flag as a question to investigate, not a conclusion. Read-only.

Guide: Bank reconciliation

Accounting → Bank Reconciliation matches your bank statement to your books, step by step:

1. Choose the bank account and the statement period.
2. Import the statement (its lines: date, description, amount).
3. Reyuko auto-matches each statement line to a recorded cash/bank movement by amount and date; you confirm the good matches and unmatch any it got wrong.
4. For statement lines with no counterpart in your books — bank fees, interest, charges — create a quick journal on the spot (Dr/Cr the bank account against a fee or income account) so they exist in your ledger too.
5. Finalize: book and bank now agree; any still-unmatched item stays visible for follow-up and carries to the next reconciliation.

This is how you catch missing entries and bank charges you didn't know about.

Guide: Fiscal periods & closing

Accounting → Fiscal Periods defines your accounting periods (normally one per month) and closes them. Each period has a status: open (you can post into it) or locked (closed).

Closing a period, in order:

1. Finish the month's transactions and run depreciation (see the Depreciation guide).
2. Close the period. This locks it — no one can post or edit into it — and runs the period-end engines:
   • FX revaluation — restates open foreign-currency balances to the closing rate (reversed next period).
   • Deferred-revenue recognition — books the earned portion of subscriptions/advances.
   • Accruals and their reversing entries.
3. Repeat month by month; closing in sequence keeps finished months final and auditable.

Year-end additionally closes the revenue and expense accounts into retained earnings (net profit or loss for the year). To correct a closed period, reopen it, make the fix, and close again.

Guide: Currency revaluation

At period close, any open foreign-currency balance — a USD receivable, a foreign-currency payable, a foreign bank account — is worth more or less in your base currency than when it was booked, because the rate has moved. Revaluation (PSAK 10 / IAS 21) restates these to the closing rate.

Example: a USD 1,000 receivable booked at rate 15,000 (Rp 15,000,000); the closing rate is 16,000, so it's now worth Rp 16,000,000 — an unrealized gain of Rp 1,000,000:

A drop in the rate posts the mirror loss. This gain/loss is unrealized and auto-reverses at the start of the next period, because the real result is only known when the customer actually pays — the realized FX difference (invoice rate vs payment rate) is booked then, on the payment. Revaluation runs automatically as part of period closing; you don't post it by hand.

Guide: Payroll — salary and its taxes

Payment → Payroll computes and posts the monthly payroll. For each employee it takes the gross salary, subtracts employee deductions (income tax PPh 21, and the employee share of BPJS social security), adds the employer contributions (employer BPJS), and arrives at the take-home net. The rates and brackets (PTKP, PPh 21, BPJS) come from your country locale.

Fields for a run: the period (month/year) being paid, the employees included (their base salary, tax status/PTKP, and BPJS settings come from each employee's record), the method — netto (tax deducted from the employee) or gross-up (the company bears the PPh 21, so the employee gets the full gross) — and the salary-expense and payable accounts the run posts to.

Posting one payroll run:

Then you pay the salaries (Dr Salary payable / Cr Cash), and later remit the salary taxes you withheld — the PPh 21 and BPJS the company holds on the employees' behalf — to the authorities (Dr PPh 21 payable + BPJS payable / Cr Cash). A gross-up option lets the company bear the PPh 21 itself: the expense becomes gross + tax and the employee receives the full gross.

Guide: Tax payment

Payment → Tax is where you remit the taxes you've collected or owe, each with its own journal.

• VAT / GST (per period). Net the Output tax you collected on sales against the Input tax you paid on purchases and pay the difference:

  Account	Debit	Credit
  VAT Output (collected)	(output)
  VAT Input (recoverable)		(input)
  Cash / Bank		(net remitted)

  If Input exceeds Output, the excess is a credit carried forward instead of a payment.

• Withholding you deducted (PPh 23). The tax you withheld from vendors sits as a payable; remitting it is Dr PPh 23 payable / Cr Cash.

• PPh 25 (monthly corporate instalment). A prepaid instalment of corporate income tax: Dr Corporate income-tax expense / Cr Cash.

• PPh Final (UMKM 0.5%). Dr Final-tax expense / Cr Cash — a final tax with no year-end reconciliation.

Each remittance clears the relevant liability (or books the expense) so your tax accounts stay accurate.

Guide: Year-end closing & corporate income tax

At year-end, on top of the monthly closes, you finalize the year:

1. Confirm every month is closed — depreciation run, accruals and reversals done, FX revaluations posted.
2. Reconcile corporate income tax (PPh Badan). Compute the year's tax due and subtract the PPh 25 instalments already paid during the year. A shortfall (kurang bayar) is settled Dr Corporate tax payable / Cr Cash; an overpayment becomes a receivable/credit. Businesses on the UMKM final tax skip this — their 0.5% monthly is already final.
3. Close the year. The revenue and expense accounts are closed into retained earnings — net profit increases equity, a net loss reduces it — so next year's Profit & Loss starts at zero while the Balance Sheet carries forward.

The result is your final annual statements, with the books rolled cleanly into the new year.

Guide: Withholding tax (PPh)

Withholding means the payer deducts a slice of a payment and remits it to the tax office on the payee's behalf. In Reyuko it appears on two sides, plus payroll — the key is which side you are on.

When you withhold (paying a vendor for services)

Buying a taxable service, you pay the vendor the net and owe the withheld tax (e.g. PPh 23 at 2%) to the tax office. On a 1,000 service, withholding 20:

You set this on the Purchase Bill or payment. The contact's NPWP status can change the rate — for example 4% instead of 2% when the vendor has no NPWP. You remit the payable later (see below).

When a client withholds from you (getting paid on your invoice)

When your customer is the one withholding, they pay you the net and keep the tax; you record the withheld amount as a prepaid tax — a tax credit (asset) — so your receivable still clears in full. On a 1,110 invoice where the client withholds 20:

That prepaid credit is tax you've effectively already paid, so it reduces your corporate income tax at year-end.

Payroll (PPh 21)

Salary withholding (PPh 21) is the same idea applied to wages — deducted from the employee's take-home and remitted by the company. See the Payroll guide.

Setup

• Company tax profile (Settings → Company) — a "PPh 23 withholder" toggle decides whether withholding options appear at all (typically on for a domestic company).
• Tax master (Accounting → Tax) — add each withholding type (PPh 23 / 21 / final) with its rate and its payable account.
• Contact — the vendor's or customer's NPWP (and any exemption certificate, SKB) sets the applicable rate.

Remitting and reconciling

Withholding you owe (PPh 23/21 payable) is remitted in Tax payment — Dr the payable / Cr Cash. Tax withheld from you (prepaid PPh 23) is offset against your annual corporate income tax at year-end closing.

Guide: Impairment & provisions (asset write-downs)

Sometimes an asset is worth less than its recorded value — slow-moving or expired stock, doubtful receivables. Reyuko lets you write it down so the balance sheet isn't overstated. Note up front: there is no upward revaluation of fixed assets to fair value in Reyuko — a fixed asset's carrying value only decreases (through depreciation, disposal, or sale, see the Fixed assets and Depreciation guides).

Inventory write-down (lower of cost or NRV)

When stock's net realizable value falls below its cost — obsolete SKUs, damage, expiry — you write down its value without changing the quantity. From Inventory → Adjustment, choose the write-down action and the new (lower) unit value. It posts, for the shortfall (cost − new value) × quantity:

The allowance is a contra-inventory account: the goods stay on the books at cost while the allowance reduces their net value (PSAK 14 / IAS 2, lower of cost or NRV). If the value later recovers, a write-down reversal reverses it — capped at the net write-down already taken, so you never mark inventory up above its original cost.

Doubtful receivables (bad-debt provision)

For receivables you might not collect, post a provision as a General Journal: Dr Bad-debt expense / Cr Allowance for doubtful accounts (a contra-receivable). When a specific debt becomes uncollectible, write it off against the allowance; if it's later recovered, reverse the write-off. The chart of accounts already includes the allowance and expense accounts for this.

Guide: Product / service

Creating a product well is what makes the rest of the app post correctly. Open Products → Product → New.

Product type — the checkbox system

You don't pick a type from a dropdown; you tick checkboxes and the combination is the type. Five main checkboxes:

• Sold — you can sell it to customers.
• Stored — it's held in inventory (stock tracked).
• Purchased — you buy it from vendors.
• Service — it's a service (non-physical); turning this on disables stock.
• Consignment — special ownership (goods on consignment).

Plus sub-options that refine a choice: Supplies (stored/bought but expensed as operating cost, not COGS), Fixed asset (recorded as PP&E and depreciated), Consignment out / in (you're the supplier vs the retailer), Subscription/recurring, Service-in (bought from a third party and resold), and Digital/SaaS.

Together they resolve to one of 12 types, and the type decides how the item sits on the balance sheet, how it's expensed, and which posting accounts are wired in — so you rarely choose accounts by hand:

Pick the combination that matches how the item really behaves — that's what makes every downstream sale, purchase, and stock movement post to the right accounts.

Key fields. A unique SKU, the name, a category (for L2 discount and grouping), an optional group, the buy and sell prices, the base unit (and alternate units with ratios), and the currency. For stocked items, turn on manage stock, set a minimum stock for low-stock alerts, and choose the COGS method (Average / FIFO / LIFO / FEFO). Mark it taxable and pick the tax; inclusive tax means the sell price already contains tax. You can add a product discount with a date window (L1), attach images, and link up to four vendors.

A product that has ever been used in a transaction can't be deleted — mark it inactive instead. Services use the same form with the Service checkbox on, which disables stock and swaps COGS for a cost-of-service entry.

Guide: Contacts (create / edit)

Open a contact list (Contacts → Customers / Vendors / Employees) and click New. Only the name is required; the code is auto-generated.

Guide: Categories

Products → Categories organizes products into a tree (parent → child). Beyond grouping, a category can carry its own discount (L2) with a validity window, which applies on top of any group/product discount. A product in a child category uses the child's discount, not the parent's. Querying by a category includes its children.

Guide: Group products

Products → Groups bundles several products under one group SKU, useful for variants and packages. Groups are a two-level tree; only leaf groups (with no children) hold member products.

Guide: Units

Products → Units is the master list of units of measure (pcs, kg, box, hour). Each product has a base unit, and you can define alternate units with a conversion ratio (for example 1 box = 12 pcs) so you can buy or sell in whichever unit is convenient while stock is tracked consistently in the base unit.