InEx Ledger
Contact us

Operating manual

How to use InEx Ledger

This guide explains the live bookkeeping workflow: what each area does, what to enter, what matters, and what to avoid. If you are unsure where to start, work through the sections in order once. After that, come back only to the part you need.

Shortest useful path

  1. Finish onboarding with your real business name, region, and first workflow.
  2. Add the account where the business money actually lives.
  3. Import or enter transactions and review your categories.
  4. Attach receipts, notes, and support files to the real record.
  5. Use edge-case fields only when the transaction is not simple.
  6. Run exports when you want a review package or CPA handoff.

Start here

1. What the app is for

InEx Ledger is a serious bookkeeping app for solo operators. Its job is to help you keep clean, support-backed records without the weight of a giant accounting suite. It is not a CPA replacement. The app works best when you use it to keep the facts straight:

  • What money came in.
  • What money went out.
  • Which account it came from or went to.
  • Why it happened.
  • What proof exists for it.
If you are new: do not try to perfect every record on day one. First make sure every real transaction exists. Then clean up categories, proof, and edge cases.
If you are behind: use CSV import or batch entry to get caught up, then review the odd transactions one by one.

First-run flow

2. Onboarding: what it asks and why it matters

Onboarding is where the bookkeeping workflow gets its first shape. It saves setup information that affects your first account, your opening workflow, and the guidance the app shows after setup.

What to enter

Work type
Choose the option closest to what you actually do. This is used for guided setup and starter guidance.
Your name or trade name
Use the real business-facing name you want tied to the records.
Primary account type
Pick the first account the app should create for you.
Account nickname
Give the first account a useful name like "Primary Checking" or "Business Visa".
Region and province/state
These control labels, tax hints, and region-specific guidance.
Start focus
This decides where the app sends you right after onboarding: transactions, receipts, mileage, or exports.

What happens after you save

  • Your onboarding details are stored in the account.
  • Your starter account is created if one does not already exist.
  • The app preserves the workflow you chose as your start focus.
  • If you start on a Pro trial, the app can send you to the billing decision page once before it opens that saved workflow.
  • Guided setup reminders can use your work type instead of showing generic filler.
If you picked the wrong thing, do not panic. You can still fix the business profile, accounts, and categories afterward.

Foundation

3. Business setup and scope

Business profile

Open Settings and complete the business profile carefully. This affects export labels, PDF output, region guidance, and the way the app frames your bookkeeping workflow.

  • Use the legal or true operating name, not a throwaway nickname.
  • Choose the correct entity type if the app asks for one.
  • Keep address, tax ID, and fiscal-year settings current.
  • Do not mix two real businesses into one profile just to "keep it simple."

Active business vs all businesses

Some pages let you switch between the active business and the all-business reporting view. This matters a lot.

  • Active business is for normal daily bookkeeping and editing.
  • All businesses is for combined reporting across businesses.
  • You cannot add or edit normal transactions in all-business scope.
  • If totals look strange, check the scope before you assume the math is wrong.
Simple rule: if you are entering or editing data, stay in the active business. If you are comparing businesses, use the all-business view.

Daily work

4. Transactions: the main workflow

This is the page you will use the most. A good transaction record should answer five questions: when, what, how much, which account, and why.

How to enter a basic transaction

  1. Choose the correct date.
  2. Write a short description that a stranger could still understand later.
  3. Enter the amount as a positive number.
  4. Choose Income or Expense.
  5. Select the account where the money actually moved.
  6. Select the category that explains the business purpose.
  7. Attach the receipt if you have it.

What the controls mean

Cleared
Use this after the transaction matches the bank or card statement.
Review status
Use this when something still needs a human decision or follow-up.
Note
Use this to explain anything the raw description does not cover.
Receipt
This is the proof. Attach it whenever one exists.

Undo, checkboxes, and row actions

  • The checkbox on the left side of the row is what opens the Edit/Delete popup for that transaction.
  • The popup appears near the checkbox on purpose. It should not open randomly elsewhere on the page.
  • The Undo button in the table header restores archived transactions.
  • Undo is not limited to one restore anymore. The app keeps a recent stack and lets you restore several archived items in order.
If you accidentally delete a transaction, use Undo right away before doing unrelated cleanup. It is much easier to restore recent records than to re-create them from memory.

Recurring transactions

Use recurring templates for things that repeat on a schedule: retainers, subscriptions, rent, software, or fixed monthly charges.

  • Create the template once.
  • Choose the cadence: weekly, biweekly, monthly, quarterly, or yearly.
  • Use Post next when you want to create the next entry immediately.
  • Pause a template instead of deleting it if the charge may come back later.

Catch-up tool

5. CSV import from your bank or card

CSV import is for getting real transaction rows into the ledger faster. It is not magic. You still need to review what came in.

  1. Open the Transactions page in the correct active business.
  2. Open the CSV import modal.
  3. Choose the destination account. This is where the imported rows will land.
  4. Select the CSV file exported from your bank or card provider.
  5. Run the import and read the result summary before you close the modal.
  6. Reloaded transactions will appear in the real transactions table. Review them before export time.
Best use case: when you are behind and need the raw rows in the system quickly.
Bad use case: importing messy data and assuming the categories, notes, and edge cases will fix themselves.

Proof

6. Receipts and supporting evidence

A receipt is the support for the record. The goal is not just to store a picture. The goal is to make the transaction defendable later.

  • Upload the receipt as soon as possible while you still know what it is.
  • If one document supports multiple business facts, explain that in the note.
  • If the vendor email or portal is the only proof you have, attach that instead of leaving nothing.
  • If the receipt is missing, keep the transaction and leave a note immediately.
  • Use the Receipts page to review what is attached and what still needs work.
If you must choose between a perfect category and missing proof, get the proof first. You can fix the category later much more easily than you can rebuild a missing receipt trail.

Travel records

7. Mileage

Mileage needs enough detail that you can explain the trip later. The minimum useful record is: date, purpose, distance, and where the trip started and ended.

  • Record business trips only.
  • Keep the purpose short but specific.
  • Use one unit consistently.
  • Fix mistakes early so the export stays clean.
"Client visit," "supply pickup," or "job-site estimate" is useful. "Trip" is not useful.

Handoff layer

8. Exports, PDF, CSV, and export history

Exports are how you turn your working ledger into something ready for review, filing prep, or a clean handoff package.

CSV export

  • Use CSV when you want the underlying rows and columns.
  • Use it for spreadsheets, review, sorting, and external analysis.
  • Check business scope and date range first.
  • If the export looks wrong, the first suspect is usually the filter or scope.

PDF export

  • Use PDF when you want a cleaner human-readable package.
  • Use it for summaries, handoff, and quicker review before opening the raw data.
  • Support pages and summaries are built from the same source data, so fix the books first if the PDF looks wrong.

Export history

The export history area exists so you can see what was generated and download the output again when needed.

  • Use history when you need to confirm what was exported before.
  • Use fresh exports after major cleanup instead of assuming an older file is still the right one.
  • If a PDF or CSV looks wrong, fix the source records and generate a new export.

Collections and follow-up

9. Invoices, replies, and the messages queue

Invoices

  • Create and send invoices from the app when you want the billing record tied to your books.
  • Keep invoice numbers, customer details, and follow-up history clean because exports and support workflows depend on them.
  • If an invoice needs correction, update the invoice record instead of trying to remember the change later by email alone.

Messages

  • The messages page is currently best for invoice replies, support requests, and verified-contact threads.
  • Do not treat it like a general live chat inbox for every customer conversation yet.
  • If a live in-app support contact is unavailable, the app falls back to support.inex@gmail.com.

Advanced entries

10. Edge cases: use the extra fields only when you need them

Foreign currency

  • Set the source currency to the real currency of the original transaction.
  • Enter the source amount before conversion.
  • Use the exchange-rate field and date to record how the amount was normalized.
  • The small live reference box can suggest a rate, but it is advisory only. You still need to confirm the final rate independently.
  • Use the "Use rate" action only if it matches your actual support.

Split-use and non-deductible items

  • Use split-use when something is partly business and partly personal.
  • Record the full amount and enter the personal-use percentage.
  • Use non-deductible when the transaction belongs in the books but should not be treated as deductible.
  • Leave a note when the reason is not obvious.

Capital items and indirect taxes

  • Mark long-life purchases like equipment or furniture as capital items.
  • Do not try to force depreciation math into a normal expense row.
  • Use the indirect-tax amount field for GST/HST/QST or sales-tax detail when relevant.
  • Keep the source invoice because it proves both the base amount and the tax amount.

Review status

  • Use review status to mark records that still need a decision.
  • Use review notes to explain the question clearly.
  • Do not leave confusing records unlabeled and hope you remember later.

Protection

11. Security, MFA, sessions, and account control

MFA

  • Turn MFA on unless you have a real operational reason not to.
  • Use the Verify flow to confirm it is working.
  • Use the cancel action during MFA setup if you opened the flow by mistake.
  • Only turn MFA off when you understand the security tradeoff.

Sessions and sign-in behavior

  • Sign out on shared or borrowed devices.
  • Review active sessions if you suspect another device is still logged in.
  • Change your password if you suspect exposure.
  • Keep business boundaries clean instead of using one account or business as a dumping ground.

Deadlines

12. Tax reminders and payment planning

Tax reminders are there to reduce deadline surprises. They are prompts, not final tax advice.

  • Use reminders to see upcoming installment due dates and draft estimates earlier.
  • Always confirm the amount and payment destination with the relevant tax authority before you pay.
  • If the reminder looks wrong, check your region, business profile, and source records before you trust the estimate.

Access control

13. Billing, plans, and feature access

Your plan affects what parts of the product are available. The billing pages manage checkout, subscription state, and reactivation flows.

  • Use the subscription page when you want to review or change plan status.
  • If you are trialing or reactivating, follow the in-app billing flow rather than starting a new unrelated checkout session.
  • If a feature does not appear, check whether it is gated by plan or by business scope.
  • If checkout fails, do not keep hammering the button. Read the message first.

Fixes

14. Troubleshooting and common mistakes

  • If totals look wrong, check the business scope and date filter first.
  • If the app will not let you add or edit a transaction, make sure you are not in all-business scope.
  • If a receipt is missing, keep the transaction and add a note instead of deleting the evidence trail.
  • If a CSV import looks incomplete, confirm the file and destination account before rerunning it.
  • If the exchange rate looks off, check the currency, date, and your own supporting statement before using the suggested rate.
  • If the export looks wrong, fix the source data and create a fresh export.
  • If a transaction needs to be restored, use Undo before you do unrelated edits.
  • If something still feels random, slow down and verify the scope, account, category, and date. Most bookkeeping errors come from one of those four fields.

Boundary

15. What InEx Ledger does not do

InEx Ledger helps you keep cleaner books. It does not magically make every judgment call for you.

  • It does not replace a CPA, attorney, or tax preparer.
  • It does not make a questionable expense deductible just because it is recorded.
  • It does not turn missing proof into good proof.
  • It does not remove the need to review currency conversions, split-use items, capital items, or tax treatment.
The app succeeds when the books are cleaner, the evidence is easier to find, and the handoff to a reviewer is shorter and less painful.