Create organization from Business Register (Äriregister) or manually, then verify profile details.
Set fiscal preferences: base currency, tax setup, invoice numbering.
Add contacts/units from Business Register (Äriregister) lookups where available, CSV import,
or manual creation.
Set up chart of accounts and key bank accounts.
Run one end-to-end flow: Quote -> Order -> Project -> Invoice.
Review Bills Import and Reconciliation for incoming operations.
Important:
to send invoices, complete organization company data first,
especially Bank details
in
/settings/organization/company-data
. Without this, sending is blocked.
Recommended invoice defaults
(same Company Data page):
Invoice footer / notes
Payment terms (days)
Invoice number prefix
Invoice line styling (header, row, summary, footer)
Payment defaults:
Default receive payment account
Default spend payment account
Invoice appearance customization:
adjust line thickness and color for table header, row separators, summary totals, and footer lines.
Split footer notes into 1–4 columns with independent line colors and multi‑line text.
A live PDF preview reflects changes instantly.
Invoice logo and PDF size:
you can add a logo (PNG/JPG, max 30 KB). Netra invoice PDFs are optimized and typically very
small (often around ~1 KB without logo). Adding a logo increases the PDF file size.
Data portability:
in
/settings/organization/company-data
use Company data export
to download ledger, chart of accounts, taxes, and linked
attachments. This lets users leave the platform with their full business data.
By Role
Start from the path that matches your role.
Owner / Admin
Organization setup and company data
Users, roles, and access control
Email, e-invoice, bank connections
Member (Operator/Accountant)
Sales workflow and invoicing
Bills import and reconciliation
Rates, reports, and VAT routines
Viewer
Read-only access to documents
Review dashboards and reports
No posting or settings changes
Before You Start
Quick preflight checklist to avoid setup and posting issues.
Organization and legal company data verified.
Bank details completed in /settings/organization/company-data.
Chart of accounts and taxes configured.
Currencies and rates configured for multicurrency workflows.
Core contacts/units imported or created before daily operations.
Authentication
URL: /users/log-in
Netra supports three login methods so teams can choose the safest and easiest workflow.
Email magic link:
user enters email, receives a login link, and access is
granted after opening that link.
Google sign-in:
user authenticates via Google OAuth and returns to Netra.
Password login: existing users can sign in with email + password.
Account Settings & Passkeys
URLs: /users/settings, /users/mode
Email:
change the login email; the new address must be confirmed from a link.
Password:
set or change the password used alongside magic links and Google sign-in.
Passkeys:
register a passkey (Touch ID, Face ID, Windows Hello or a security key) and sign in without a password on that device.
Mode:
people who are both accountants and apartment owners switch between the accounting workspace and the owner portal at /users/mode.
Keyboard Shortcuts
Netra has built-in keyboard navigation. Hold Alt
to see context hints on screen.
Global navigation
Esc: back (close modal first if modal is open).
Alt+Esc: forward.
Alt+I: open Invoices.
Alt+B: open Bills.
Alt+N: create new (invoice/bill, depending on page).
Alt+F: open filters and focus search input.
List/table navigation
↑ / ↓: move row selection in data tables.
Enter: open selected row.
← / →: previous/next page where arrow paging is enabled.
Invoice shortcuts (contextual)
Alt+P: post invoice (or form post action).
Alt+S: move to draft / save draft.
Alt+E: email invoice (or edit, depending on visible action).
Alt+C: clone invoice.
Alt+V: open PDF preview.
Alt+M: open email preview.
Alt+R: receive payment (when available).
Alt+D: download e-invoice file.
Bill shortcuts (contextual)
Alt+P: post bill.
Alt+S: move bill to draft / save.
Alt+E: edit bill.
Dashboard shortcuts
Alt+I: Invoices
Alt+B: Bills
Alt+C: Contacts
Alt+R: Reconcile
Alt+U: Bills Import
Appearance & Language
Users can personalize appearance (theme/look) so teams can work with different visual styles.
Default product language support: EN, ET, and RU.
If your organization needs additional language support, please contact support.
First Organization Setup
After first login, the user creates an organization before using accounting features.
Choose Create from Business Register
or Manual create.
If using registry, search/select company and import profile data.
Verify legal name, registration code, tax/bank details, and defaults.
Save organization and continue to dashboard setup.
Settings Overview
URL: /settings/organization
The settings hub groups every organisation-level screen.
Company data
/settings/organization/company-data: legal name, registry code, VAT number, address, bank details, invoice defaults and appearance, the invoice logo, and a separate square
app logo
shown as the organisation mark in the sidebar (cropped in the browser on upload).
/settings/organization/invoice-preview.pdf: live preview of the invoice layout.
/settings/organization/company-data/export: full company data export as a ZIP of CSV files and attachments.
General
/settings/organization/users: members and roles. /settings/organization/audit-log: change history.
/settings/organization/api-tokens: tokens, scopes and AI settings. /settings/organization/menu: navigation customisation.
/settings/organization/email-settings
and /settings/organization/e-invoice-settings: delivery channels, see Invoice Delivery.
/settings/organization/reminders: automatic payment reminders, see Payment Reminders.
Finance
/accounts: chart of accounts. /taxes: VAT codes and rates. /rates: allocation and price rates.
/settings/organization/currencies: enabled currencies and precision. /settings/organization/opening-balance: opening balances with equity automation.
/settings/organization/measure-units: units of measure used on lines.
Dimensions
/units
and /expenses/meters: property units and meters for associations.
Multi-Organization
One user can manage multiple organizations/companies in the same Netra account.
Use the organization switcher in the top bar to move between companies.
Netra keeps you in the same area/view when switching organization (for example from one report
to the same report in another organization) whenever that route is available.
Use Manage organizations
to create or access additional organizations.
Organization-specific settings and data (accounts, documents, reports) remain isolated per organization.
Manage organization access and user permissions from organization users settings.
Invite and roles
Invite is sent by email.
Role options: Viewer (read-only), Member (read & write), Admin, Owner.
Use least required access level and promote only when needed.
My settings
Each user can update personal account settings in /users/settings.
This includes own account preferences, while organization-level permissions are managed by org admins/owners.
Role Permissions
Viewer: read-only organization access.
Member: read/write for daily operations.
Admin: full operational control and user/settings management.
Owner: highest level, including ownership-level control.
Organization Currencies
URL: /settings/organization/currencies
Manage currency list used by the organization. Users can add any currency needed for operations.
Add currencies used in sales, purchases, banking, and reporting workflows.
Currency setup works together with rates management for multicurrency reporting.
Keep active currencies aligned with real business usage to simplify document and account setup.
Audit Log
URL: /settings/organization/audit-log
Audit Log shows the timeline of important organization-level actions and changes.
See who changed key data and when the change happened.
Use it for internal control, troubleshooting, and accountability checks.
Useful during month-end review and compliance workflows.
Navigation Menu Customisation
URL: /settings/organization/menu
Hide whole menu sections or individual items per organisation so the navigation only shows what that organisation uses. A small association can hide Stock, Fixed assets and the sales pipeline; a trading company can hide Units and Sharing bills.
Hidden items stay reachable by URL and keyboard shortcut; the setting only affects the menu.
The preference is per organisation and applies to all its users.
Bring an existing customer or supplier list into Netra with a CSV file, and take it out again at any time.
Template:
download /contacts-template
to get the expected columns.
Import:
upload the CSV at /contacts/import, check the row preview and confirm. Rows are matched to existing contacts where possible.
Export:/contacts.csv
returns all contacts of the active organisation.
Single contacts can also be created from the Estonian Business Register lookup on the contact form.
Sales Workflow Board
URL: /sales/workflow
The board is the operational view of the full sales lifecycle: Quote -> Order -> Project -> Invoice.
It is designed for daily pipeline control, not only document listing.
Board structure
Columns show Quotes, Orders, Projects, and Invoices side by side.
Search/filter is global and narrows matching rows across all columns.
Each row helps connect customer + document + project context in one place.
Typical lifecycle
Create Quote and assign customer + row-level projects where needed.
Accept Quote and create Order from it.
Move Order through execution statuses.
Create Invoice from Order when work is complete/approved.
Approve/send invoices from Invoices module (single send or mass send).
Project behavior
Projects are linked at row level, so one Quote/Order/Invoice can include multiple projects.
Project pages aggregate related sales documents for operational visibility.
When multiple projects exist in one document, board rows show mixed/project context instead of a single-color indicator only.
Status and control points
Quote status controls conversion to Order.
Order completion status controls when invoice creation should happen.
Invoice sending is done after approval; draft invoices are editable and unsent.
Color-coded statuses on board align with other sales pages for consistency.
Best practice
Use board for daily triage; use individual forms for detailed editing.
Keep project naming/status clean to make board tracking reliable.
Use Projects view when you need cross-customer view by project/release cycle.
Quotes, Sales Orders & Projects
URLs: /sales/quotes, /sales/orders, /projects
The sales pipeline is made of separate documents that link to each other. The Workflow Board shows them side by side; these screens manage each type in detail.
Quotes:
create a quote with lines, attach files, preview and send it by email from /sales/quotes/:id/email. Accepted quotes continue as orders.
Sales orders:
confirmed customer orders that carry the agreed lines until invoicing.
Projects:
group quotes, orders and invoices of one engagement so that its history and totals are visible in one place.
Every document keeps a link to the contact and can be opened from the contact page.
Recurring Invoices
URL: /invoices/recurring
Recurring invoices generate and deliver a copy of an invoice on a schedule, for example monthly rent, service fees or association payments.
Schedules
are shared: define a name, a monthly frequency with an interval in months, and reuse it for many invoices.
Each recurring invoice has a start date, an optional end date, and anchor dates that decide the invoice date and due date of every generated copy.
The list shows the next invoice date, the last successful run and the last error, if any. A recurring invoice can be paused and resumed.
Generated invoices use the delivery method of the source invoice (email, e-invoice or internal) and appear in the normal invoice list.
Generation runs in the background. Check the recurring invoices list after the scheduled time if a copy seems to be missing; the last error column explains failed deliveries.
For Billberry delivery, Billberry credentials must be configured in organization settings.
For Internal delivery, recipient organization must be resolvable (typically by registration
code/internal organization link).
Behavior by method
Email:
sends invoice by email and records delivery history.
Email delivery includes:
Inline MJML-based email preview content (readable directly in mailbox).
Attached invoice PDF file.
E-invoice (Billberry): sends XML via Billberry connector.
Internal:
creates/updates a Bill Import entry in
/bills/import
(Recent Imports), then user finishes via Basic/Detail import flow.
Combined modes:
execute both configured channels and report partial failures if any.
The invoice PDF uses the Netra "Ledger" layout on A4: issuer and logo, a fact strip with date, due date,
reference and amount due, the payer and property unit, the line table, then a payment panel (IBAN,
reference, amount) beside the totals. Footer columns, rule colours and the logo come from company data.
Files are around 40 KB and render identically in Preview, Mail, Chrome and Acrobat.
Common errors:
missing company bank details, incomplete email settings, or
delivery method mismatch for recipient settings.
Email Delivery Settings
URL: /settings/organization/email-settings
Configure how outgoing emails are sent for invoices, quotes, and purchase orders.
Available sending options
Use system email (managed sender).
Use Gmail.
Use Outlook/Hotmail.
Use a private SMTP server.
Practical guidance
System email is fastest to start with and requires the least setup.
Mailbox providers (Gmail/Outlook) are useful when sender identity must match user mailbox.
Private SMTP is best for organizations with custom domain mail infrastructure.
Prepayments & Overpayments
When a customer or supplier pays more than a document total, the extra amount is stored
as a prepayment and can be applied to future invoices/bills for the same contact.
Customer prepayments (Ostjate ettemaksed)
Example: invoice 200, payment 210 → 200 is allocated, 10 is booked to Customer Prepayments (215).
Next invoice for the same contact auto-applies the prepayment on approval.
No new bank transaction is required.
Supplier prepayments (Ettemaksed tarnijatele)
Overpaying a bill books the extra to Supplier Prepayments (150)
as an asset.
The next bill from the same supplier auto-applies that prepayment on approval.
Payment Reminders
URL: /settings/organization/reminders
Automatic reminders for overdue invoices. Off by default; switch them on per organisation.
How it works
Choose steps
as days past due, for example 7, 21. Every morning Netra
sends, for each posted invoice that still has an open amount, the highest step reached, once. A step is
never repeated and an earlier step is never sent after a later one. An invoice paid in between gets
nothing more.
Invoices overdue longer than the cut-off
(default 90 days) are left for a person, so
switching reminders on does not mail years of old debt.
Payers can be excluded with the Send payment reminders
checkbox on their contact card.
Payers without a real email address are skipped.
The email
Subject "Payment reminder: invoice N", in the payer's language, with the open amount, due date, days
overdue, your IBAN and reference number, and the invoice PDF attached. Sent from the account chosen in Email Delivery Settings.
Your own text can replace the default sentence. Preview email
shows the real message
and Send test to me
mails it to your own address.
Manual sends and history
The settings page lists the invoices due for a reminder today with a
Send
button per
row, plus counters for this month, in total and failed. Every send is logged.
The invoice page has a Payment reminders
block with the history and a Send reminder now
button.
Bills Import Module
URL: /bills/import
This is the main intake module for incoming bills. It supports manual uploads, internal invoice
delivery intake, and e-invoice/Billberry intake in one workflow.
Product positioning: this flow is similar to tools like CostPocket/Envoice, but built directly
inside Netra with accounting-ready review and posting.
How bills arrive
Manual upload:
drag-and-drop or click anywhere in upload zone (PDF, image,
EML, XML).
EML support:
users can download an email as .eml
and upload it
directly; invoice data is extracted from the email content/attachments.
Internal delivery:
invoices sent with Internal method appear in Recent
Imports for review.
E-invoice / Billberry:
fetched documents are listed in Recent Imports and
processed in the same review flow.
Processing modes
Detail:
keep detailed lines as extracted/imported, including per-line VAT and
accounting dimensions.
Basic:
summarized import for quick posting when full line detail is not needed.
VAT handling supports both VAT included
and VAT excluded
logic per row.
Vendor matching and creation
System tries to match vendor automatically (email, registration code, tax ID, name).
If registration data is available, vendor lookup can use Business Register integration.
If vendor does not exist, a new vendor contact can be created and saved to Contacts.
Vendor templates (automation)
Every saved bill teaches Netra how that vendor's lines map to accounts and VAT. The next import from
the same vendor arrives prefilled; lines whose description matches a remembered line get its account,
others get the vendor's default.
Templates are managed in
/bills/import/rules
(Vendor templates). Older text rules and OCR hints still work and live on the same page.
An import whose vendor, lines, accounts and date are all known is marked ready;
Save N ready
in the queue posts them all at once, Save and next
in the
review moves through the rest one by one.
Receipts for payments already posted
If the bank line was already posted straight from the statement, saving the receipt replaces that
direct posting with the bill and its payment, so nothing is booked twice. See Undocumented postings.
If a bill with the same vendor, number and amount already exists, the review offers to
attach the file
to it or mark the import as a duplicate.
After save
Saved documents are created as Bills and appear in /bills.
Bills can still be opened and edited later if needed.
Recent Imports view includes filters (date range and status) to resume work quickly.
Purchase Orders
URL: /purchases/orders
Purchase orders record what you have ordered from a supplier before the bill arrives.
Create an order with supplier, lines and expected amounts, then email it to the supplier from /purchases/orders/:id/email.
When the supplier bill is imported, compare it against the order before posting.
Orders use the same items catalog as bills and invoices.
Bank reconciliation can be done in three main ways: import an Estonian bank statement file
(for example from internet bank), connect directly via GoCardless to sync bank statements,
or use LHV Connect for direct LHV bank statement access.
Chart of account bank fields
In /accounts/:id/edit, bank account rows use
Account address / IBAN
for bank-transaction connection and account identification.
The reconciliation hub lists every bank account with its unreconciled transactions. Open an account to
get the inbox: what Netra can settle by itself sits on top, the rest is grouped by
counterparty so one decision covers many lines.
The inbox
Confident matches
pair a bank line with exactly one open invoice or bill by reference
number, document number, amount, date and counterparty. Accept all
posts them in one
go; every match shows its evidence.
Bundles
group the remaining lines by counterparty (IBAN, card merchant or name) and
propose the account used for that counterparty before. Pick the account once and post the bundle.
Done today
lists what was posted with an undo, and Replace with bill
when the receipt arrives later.
Statement CSV files can be imported manually for banks without a connection.
Working a transaction
Match
it to an open invoice, bill or journal. Netra suggests matches by amount, reference and counterparty.
Post
it directly to an account when there is no document, with a preview of the journal that will be created.
Link
it to an existing journal entry, or delete
a transaction that was imported twice.
Create a rule
from the transaction so future lines from the same counterparty are handled automatically, see Bank Rules.
A confirmed reconciliation can be undone; the journal is reversed and the transaction returns to the open list.
The dashboard's "needs attention" list and the Netra Assistant daily review both read from the same open transactions, so clearing the hub clears them too.
Document value sources: Manual value, Invoice number, Payment reference, Note, Date, Due date,
Contact name, Total.
Custom mode supports separate tx/doc operators and left/right values.
Actions by kind
Invoice/Bill rules:
allocation lines to accounts (amount or percent), optional
contact override, optional document lookup helper.
Journal rules:
one or more journal rows; bank row can be added manually or auto-generated.
Journal rows support static debit/credit amounts or transaction-side dynamic amount direction.
Result of applying a rule
A journal/payment entry is created according to rule configuration.
Bank transaction is marked as matched.
For invoice/bill kinds, payment allocation links are created to document balances.
In /journals, the Reconciled
column shows Yes
for
settled entries (bank-matched payments, allocated payments, and document rows with zero outstanding).
Undocumented Postings
URL: /finance/undocumented
A payment posted straight from the bank statement proves that money moved, not what was bought. Until
a receipt or invoice exists the amount counts as an undocumented payment for income tax
(TuMS § 51 (2) 3; tax 22/78 of the net amount, declared on TSD annex 6 by the 10th of the next month).
Every direct posting from the bank gets a document status: missing, documented,
not needed, or declared. Accounts such as bank fees can be marked "no source document expected" in the
chart of accounts, so their postings never appear here.
The page lists missing documents by month with the exposed amount and the tax if declared. From each
row you can add the receipt
(opens the import with the posting preselected),
mark that you have it
elsewhere, mark it not needed, or declare
it; Declare month
handles a whole month.
The dashboard queue shows the count, and the journal list marks such postings with a chip. When a
receipt is imported later, saving it replaces the direct posting automatically.
Journals, Activity & Notes
URL: /journals
Every invoice, bill, payment and manual entry is a journal. The journals list is the general ledger view; manual journals are created from /journals/new.
Journal lines carry account, debit or credit, currency and optional dimensions. Status changes (draft, posted) are recorded.
The journal page has an Activity and notes
feed: add a note, load older activity, and see what changed field by field.
Each activity row shows the actor: a user, Netra Assistant, an MCP client, or the system. This is the audit trail for AI-driven changes.
Nothing is hard-deleted. Reversals and status changes stay visible in the feed.
Fixed Assets
URLs: /finance/assets, /finance/assets/categories
The fixed asset register tracks equipment, vehicles and property with their depreciation.
Asset record
Code, name, category, currency, acquisition date and the date placed in service.
Cost, salvage value, useful life in months and depreciation rate. The register shows monthly and accumulated depreciation and the carrying value.
Location, cost centre, notes, and an optional link to a loan when the asset is collateral.
Filter the list by active or disposed assets.
Categories
Categories hold the default accounts: asset, accumulated depreciation, depreciation expense, revaluation surplus and deficit, realised gain and loss. New assets inherit them.
Automatic depreciation runs, write-offs and revaluations are on the roadmap; today the depreciation journal is booked manually using the figures shown in the register.
Loans
URL: /finance/loans
Register a loan with its type (short or long term), currency, principal, annual interest rate, start and end dates and notes.
Add payments with date and amount, split into principal and interest components. Netra books the corresponding journal so the outstanding balance and interest expense stay in sync with the ledger.
Loan status (active or closed) and the outstanding amount are shown in the list.
Fixed assets can reference a loan when they serve as collateral.
Currency Operations & Investments
URLs: /finance/currencies, /finance/portfolio
Beyond invoicing in foreign currencies, Netra records buying, selling, transferring and swapping currencies and crypto assets as proper accounting operations.
Operations ledger
at /finance/currencies
lists every buy, sell, transfer and swap with amounts, fee and rate.
The forms for each operation show a preview of the journal lines
before you approve. Operations move from Draft to Approved.
Realised and unrealised gains follow the rules described in Reports, VAT & Compliance; high-precision crypto amounts are supported as base or foreign currency.
Investments portfolio
at /finance/portfolio
tracks other holdings such as securities or deposits.
Generated package can be used for compliance workflows and archival/export in company records.
Common errors:
missing opening balances, missing rates, incomplete company metadata,
or unresolved VAT mapping before export.
VD Report (Intra-Community Supplies)
URLs: /reports/vd, /reports/vd.xml
The VD report (EMTA vorm VD) lists your zero-rated sales to VAT-registered
customers in other EU member states, aggregated per partner. It is filed together with the
monthly VAT return.
Where the numbers come from
Only posted sales invoices
dated inside the selected period are included.
Lines whose tax code has the type Intra-Community supply of goods
go to the
goods column (KMD line 3.1.1). Lines with the type
Intra-Community supply of goods and services to a taxable person of another Member State
go to the services column (KMD line 3.1). Set these types on your tax codes at /taxes.
Foreign-currency amounts are converted with the invoice exchange rate and rounded to whole
euros, as the VD schema requires.
The partner's country and VAT number are read from the contact's VAT ID, for example FI12345678. Rows are sorted by partner name.
Warnings
The report checks each partner before you export and lists problems above the table:
Partner has an EU supply but no VAT number: add it to the contact.
Partner has an invalid VAT number: the country prefix cannot be derived. The format is a two-letter country code followed by up to twelve characters.
Partner has an Estonian (EE) VAT number: a domestic sale is tagged with an EU supply tax code, so fix the invoice line.
Filing
Pick the month or a custom start and end date, review goods, services and totals per partner.
Click XML
to download the declaration file and upload it in e-MTA. Partners with warnings are left out of the XML, so clear the warnings first.
The same figures appear on the VAT (KMD) declaration, so run both reports for the same period.
Rates Management
URL: /rates
Currency rates are managed in this page and used by reporting and revaluation logic.
Rates support multicurrency report consistency across Balance Sheet, P&L, and Trial Balance.
Balance Sheet revaluation uses system rates to automatically revalue relevant balances.
Keeping rates complete and up to date is important for accurate unrealised FX values.
Units Concept
A Unit
is a property object linked to a contact (for example apartment,
office, parking space, storage, or other rentable/ownable space).
This is useful when one owner or client has multiple properties. Instead of billing only by
contact, you can bill by contact + specific unit.
What Units enable
Invoice per unit (accurate billing by property/location).
Record bills/expenses per unit.
Share common expenses between units.
Automate invoice creation using unit ownership and allocation logic.
Typical use cases
Real estate operators managing multiple rental units per client.
Korteriühistu (apartment associations) managing properties and owner billing.
Any business where billing must be segmented by location/property.
This module is used to split shared costs (utility bills, service costs, common expenses)
between units and generate invoices automatically.
Quick flow: share expenses by period
Prepare units for monthly meter readings collection.
Set up required meters in /expenses/meters.
Create period in /expenses/periods.
Add expense item; choose Meter
type when usage-based allocation is needed.
Open Enter Readings for this period, fill unit readings, and save.
Return to preview and click Share expenses.
Period lifecycle
Create period manually or with quick month create.
Clone period to copy item setup into the next period (good for recurring monthly operations).
Add expense items and preview allocations before sharing.
Share period to generate invoices per unit/contact.
Reopen period if needed (to adjust and re-share).
Expense item types
Meter: split by consumption readings (for example kWh, m3, Gcal).
Area: split by unit area (heated area or total area m2).
Fixed: fixed amount per unit.
Unit/UOM: every item has a unit selector with practical defaults.
Default units are fast to pick, and unit value can be overridden when business-specific unit
names are needed.
Every item is linked to an accounting account and can set unit labels and price precision.
Bills and vendor auto-linking
Items can link one or multiple bills imported via /bills/import.
Bill vendors (optional)
supports one or many vendor names. Matching bills are
auto-linked for the period.
This helps recurring vendors (for example electricity, water, heating) auto-attach when new
bills arrive in later periods.
For meter items, multiple linked bills are supported in one calculation run.
Readings and calculations
Enter meter readings per unit for the period; system calculates consumption deltas.
For meter items, unit price can be derived from linked bills and applied to each unit usage.
For area items, total amount or override unit price is split by selected m2 basis.
For fixed items, amount is allocated as fixed per unit.
Price precision can be set per item to control rounding and output detail.
Preview supports filtering and sorting to validate allocations before sharing.
After sharing
Invoices are created per unit owner/contact and linked to the period.
Unit setup matters: each billed unit should have a billed contact configured.
Created invoices can be reviewed and edited later in Invoices.
Status and period filters in list view help track draft/shared/reopened periods.
Meter replacement guide
Go to /expenses/meters and open the meter.
Choose the unit and add the new meter reading information, then save.
Period allocation will account for previous and new meter parts separately, so calculation can
appear as separate rows in bill/invoice allocation output.
Correcting wrong meter readings
If wrong readings are entered, user can edit them in the Meters section.
Editing is available while the period is open (not shared/locked).
After correction, refresh preview and share/re-share period as needed.
Common errors:
missing billed contact on unit, missing readings for meter item,
or attempting to change data on shared period before reopening.
Unit Owner Capabilities
Unit owners can access their portal at /units/my.
View invoices linked to their units.
Open invoice PDFs directly from the list.
Update their contact details for the organization.
Submit meter readings (when meters are configured).
Switch between unit owner and accounting user modes from the Account menu.
Owners sign in with the same login methods and land in /units/my; no organisation membership is needed. They see their units, enter meter readings and follow invoices, payments and balances per currency.
Administrators with the manage-users permission can open the portal as a given owner. A banner shows whose view it is. Use it to enter a reading on behalf of an owner or to check what they see.
Owners edit their own contact details at /units/my/contacts/:id/edit.
Netra Assistant
URL: /assistant
Netra Assistant is the built-in AI. It works through the same MCP tools that external clients use, inside your organisation and role permissions.
Chat
Ask questions from any page. Sessions are persistent: create, rename, pin and delete them from the assistant page.
Reads are immediate. Writes ask for approval by default; an organisation can enable automatic accounting actions for the assistant.
Organisation-level AI settings (own OpenAI API key, prompt id and prompt version) are on the
API tokens
page.
Daily review and work queue
The daily review scans for duplicate bank transactions, missing source documents, pending import matches, refund pairs, safe reconciliations and suspicious bank rules.
Findings become durable work items with evidence. Review them at /assistant/review: approve, reject or apply; applied items book the change and record the assistant as actor. The dashboard shows the open count.
The same queue is available to MCP clients through the review and work-item tools.
Netra can expose organization-scoped accounting tools to ChatGPT through MCP. Start by
generating an API token, connecting https://netra.ee/api/mcp, and asking
ChatGPT to inspect the books before changing anything.
“Please check Company A books. Find unreconciled bank transactions, pending bill imports,
and likely invoice or bill matches. Ask me before creating rules, importing documents, or
confirming reconciliation.”
netra_review_books gives ChatGPT a read-only accounting work queue.
Missing payment documents can be requested with netra_request_document_for_transaction, verified against a bill import,
and converted into a bill only after approval.
Multiple small documents can be imported together with netra_import_bill_files_from_base64.
If the chart of accounts or supplier contact is missing, MCP returns suggested setup
actions for ChatGPT to ask approval before creating them.
Bank transaction reconciliation remains approval-based for writes.
Use the MCP docs
for exact connection examples and tool names.
API Tokens & Scopes
URL: /settings/organization/api-tokens
API tokens let external AI clients and integrations act inside one organisation. Owners and admins create and revoke them.
Tokens are organisation-scoped and inherit the creating user's role. The page shows the lifetime; expired tokens stop working automatically.
Scopes
limit what a token may call: read
(reports and lookups), write_accounting
(create and change documents), write_ai_approval
(approve or apply review work items), admin
(organisation setup).
Used by the MCP server at POST /api/mcp
and by the REST endpoint POST /api/bills/import
for sending documents from other systems.
Revoke a token at any time; running clients receive an authentication error on the next call.
Tool-by-tool scope requirements are listed in the MCP docs.
Placeholder Pages & Roadmap
Some menu entries open a "coming soon" page. They mark planned features and are listed here so nobody looks for missing settings.
