Manage the Largest Organizations Through One Conversation

Who is it for?

Arfinex is not just a tool for financial institutions. If your business receives money and pays money, Arfinex can be useful to you:

• An online store
• An advertising or travel agency
• A startup that has just raised its first funding
• A family business with several branches
• A distribution company or service firm
• The finance team of a multi-company group

Forex and CFD brokers, crypto exchanges and payment gateways are also among Arfinex's audiences. Their money flows are among the most complex, and Arfinex was designed with that level of detail in mind, but they are only one example

What Arfinex is not

Let's make one thing clear from the start: Arfinex builds and provides software only. Arfinex is not a bank, broker, custodian, auditor or tax adviser

Arfinex does not hold or move customer funds or digital assets. Wherever payments, asset custody, currency conversion or identity verification are involved, that work is done only through licensed providers

Tracing money: every cost followed to the end

The core idea behind Arfinex is simple: no number should exist without a source. Every movement of money is linked to its source, whether that is an invoice, a contract, a bank line, a wallet transaction, a payroll list or a gateway report. Every cost is also followed all the way to where it ends up

Example: the cost of a campaign

Picture an ordinary Tuesday. The marketing manager pays for an advertising campaign with the company card. In most companies, that payment is one line on the card statement, and at the end of the month someone writes "advertising" next to it

In Arfinex, that same payment is linked to the campaign, the campaign to the leads it brought in, and the leads to the revenue that followed. If a campaign keeps spending and returns nothing, you see it as an open question with a specific figure, not as a vague feeling in the quarterly meeting

Example: a duplicate payment

Every outgoing payment has to trace back to an approved obligation. So a second payment for the same invoice doesn't slip through quietly; it lands on the table as an exception with a named owner

The same goes for a fee that doesn't match the agreed rate, or a subscription no team owns. The goal is to see an extra cost before it repeats

A double-entry ledger as the foundation

The foundation of this work is the multi-asset financial engine and general ledger. Every deposit, withdrawal, transfer, fee, commission and settlement is an event with a balanced double-entry record

A balance is the sum of the entries, not a figure someone typed in by hand. Every mistake is corrected with an approved reversing entry, not by editing or deleting. If you are familiar with the principles of double-entry bookkeeping, the logic of this engine will feel familiar. Read more in Immutable ledger, reversing entries and the audit trail

Every number carries a reliability label

Not every number in a report is equally reliable, and Arfinex does not hide the difference. Next to every balance and every line, it shows where the figure came from:

• Verified: read from the source, with its evidence attached
• Declared: stated by someone, such as the balance of a wallet held by a colleague or a statement a partner sent over a messaging app, but not yet matched against an independent source
• Unknown: money has moved, but its counterparty has not been found in any source
• No access: a source that should have been read was not available
• Held: the line has no posting rule yet and is waiting for your decision
• Reconstructed: the figure was not read at its own moment and has been rebuilt from the source

At a glance, a manager can see which numbers can be relied on and which still need work

Precise language for discrepancies

A discrepancy whose cause has not yet been found is called an "unexplained difference", not "missing money" and not "fraud". Such a difference is never closed with a manual figure; it stays on the list with an ID, its exact place in the ledger and its age until it is explained with evidence

A difference that comes only from a different cut-off time is not treated as a real discrepancy either. If a partner's statement closes as of yesterday and your ledger as of tonight, the transactions between those two moments are shown separately. The balance is labelled "reconciled as of …", so a simple timing gap does not show up every day as a fresh discrepancy

Accounting through conversation

Accounting has always assumed that the person who knows what happened also knows how to write the accounting entry. In practice, these are usually two different people. The sales manager knows they paid the deposit for the conference hall, but doesn't know which account that payment belongs in, and doesn't need to

In Arfinex, you can create draft entries by talking or chatting. Write "I paid the deposit for next month's conference hall from the company's main account", and Arfinex prepares the suggested accounts, the currency and the link to that event's budget as a draft

You can also ask questions, in your own words:

• "How much did we spend on travel this quarter compared with last quarter?"
• "Which customers haven't paid for more than 30 days?"
• "Why is our cash balance lower than last week?"

The answers come from the general ledger, and each number shows its source

From a single instruction to controlled execution

Arfinex doesn't just answer questions, and it isn't limited to building drafts. An authorized user can describe the expected outcome in plain language and hand the full execution to a specialized agent, within the limits of their role and the organization's policies

For example, you can give the accounting agent a PDF bank statement and say: "Review this statement, match the lines against our documents and accounting rules, separate the unknown items and post the verified ones." Arfinex extracts the data, flags duplicates and exceptions, and, after the required instruction or approval, posts balanced entries and updates the bank account balance. The original file, the extracted line, the rule applied and the approver's identity stay alongside the result

The same logic applies to operational files. A spreadsheet can import a list of employees, customers, calls or payments. If the employees' call log, the customer list and the verified deposits are available, Arfinex can identify which call led to money being collected, calculate each employee's commission with a versioned rule and, after authorized approval, post the liability to the employee and the commission expense entry

A workflow whose sources, rules, owner and level of authority have been approved once can run on a recurring basis; for example, every month it can read data from the designated sources, repeat the same controls and put only exceptions or new decisions in front of the relevant owner. Recurring execution does not mean unlimited authority: any action outside the rules, above a limit or without evidence stops

Historical questions are answered from the same connected data. If prior years' information has been imported or read from the sources, a manager can ask "What was our rent three years ago, and what is it this year?" and get the answer together with the period, the currency, the underlying entries and the reliability status of each number

Scenario: what does the manager see in the morning?

Running a large organization is rarely hard because there are too few reports; it is hard because there are too many disconnected ones. The CEO gets a liquidity file from finance, the sales report lives in the CRM, contract obligations sit in another folder, HR keeps its own list and project status is tracked in a work management tool. Each may be correct, but the answer to a single management question is often scattered across several systems

In Arfinex, a manager can ask the question exactly as they would in a meeting: "What actually needs my decision today?" A good answer is not a page full of charts. A good answer is a short list of items whose source, amount, owner, deadline and next action are clear. A balance that has not been read from its source is not mixed with a verified one. A cost that has exceeded its budget is shown next to its contractual commitment. An important customer whose payment is overdue is shown with the last contact and the person responsible for follow-up

This management view does not replace each department's specialist reports. The finance director still has the ledger and the trial balance, the sales director sees the funnel and the calls, and the HR lead has access to the permitted employee information. The difference is that a cross-departmental question no longer needs days of manual gathering, provided the relevant sources are connected and the manager's access level is defined

In a management answer, Arfinex keeps four things apart: a fact that came directly from a source, an inference drawn by putting data together, a suggestion the agent offers for the next action, and a decision that only an authorized person can make. This separation keeps an AI suggestion from being mistaken for a recorded fact

Scenario: from an employee's call to a defensible commission

In many sales teams, disputes over commission don't start with the formula; they start with the question of which call actually led to a deposit. If employees, customers, calls and deposits sit in four separate files, the end of the month goes into linking rows to each other, and the result is not easy to explain to the employee or the sales manager

When this data enters Arfinex with reliable identifiers, the path becomes clear. Each call is linked to the relevant employee and customer. The verified deposit lands in the customer's record. The organization's approved rule then defines which call or set of calls qualifies for attribution, how long the waiting period is, what effect a refund has and which version of the commission rate applied in that period

The result is not just a final number. A manager can see which collections each person's commission was built from, which item is still set aside for lack of evidence and which refund needs an adjustment. After authorized approval, the liability to the employee and the commission expense entry are posted. If the organization wants, the same workflow repeats next month with the same sources and rules, and only new exceptions reach the relevant owner

This mechanism is not meant to guess the value of a call. If the customer ID cannot be linked between the call log and the deposit, the item stays for human review. If two employees were involved in one opportunity, the split method must already be defined in the versioned rule. If the rule changes, earlier periods keep the calculation from the version in force at the time, so the result remains defensible to employees and auditors

Scenario: monthly operations without starting from scratch

Real automation means the organization doesn't have to explain the same work to the software from the beginning every month. A recurring workflow is repeatable when five components are clear: the data source, the processing rule, the owner of the result, the authority limit and the stop conditions. For example, a commission workflow can read the calls file and the verified deposits on a set day, apply that period's rules, build a draft calculation and hold the items without evidence

A bank reconciliation workflow can take the new statement, separate duplicate lines, match items that have a rule against existing documents and hand the list of unknown items to the accounting owner. A recurring-costs workflow can compare subscription renewals, repeated invoices and fee changes with the previous month. A receivables workflow can show overdue customers with the last contact, the payment promise and the person responsible for follow-up

Repetition does not mean removing human control. The organization decides which result is only reported, which becomes a draft and which is posted within the approved limits. A change of destination account, crossing a limit, missing documentation, an unusual change in amount or a conflict between two sources can each be a stop condition. Every run records its time, its sources, its rule version and its result, so it is clear what was done automatically and what is waiting for a decision

The main benefit of this model isn't saving a few clicks. The benefit is that operational knowledge leaves one person's head and becomes a rule that is visible, versioned and testable. If the owner changes, the process doesn't disappear. If a manager questions a number, the answer comes from that recorded run and its evidence

Scenario: one question, several departments

Suppose a manager asks: "Where did this month's drop in cash come from, and who needs to act?" The answer may not sit in accounting alone. Part of the decrease relates to an equipment purchase, part to two customers paying late, part to the automatic renewal of a software contract and part to a prepayment for next month's event. A complete answer needs the general ledger, contracts, the CRM, the budget and the task tracker seen together

Arfinex keeps each part linked to its own source. The purchase amount comes from the entry and the invoice. The customer delay is established from the due dates and the actual deposits. The contract renewal is visible from the recorded commitment and the bank payment. The event prepayment is linked to its budget and the period in which it will be used. The agent can explain these pieces in one answer, but it does not generate the numbers itself

The output can say how much of the change in cash was planned, how much relates to late collections and which item still lacks a sufficient explanation. An owner and a deadline can also be set for each action: sales follows up on collection, procurement reviews the unused renewal and finance approves the classification of the prepayment. Instead of searching through files, the manager talks about decisions

The same logic works for other questions too: "Which hires still don't have a complete contract?", "Which project has used its budget but hasn't delivered?", "Which customer generates revenue but has unusually high support costs?" An answer is given only when the necessary data and permissions exist. Missing data is reported as missing data, not hidden behind a guess

Scenario: from a management question to a trackable action

An answer is only complete when it leads to a specific action. Suppose the answer to the manager's question shows that two key customers are past due, an unused software contract has been renewed and one branch's shipping costs have risen compared with the average of the previous three months. Arfinex can route each item, with its evidence, to the relevant owner: collection follow-up for the account manager, the renewal review for procurement and the cost-increase analysis for the branch manager. The owner, deadline and action status stay with the issue itself, so the management answer doesn't turn into a list that gets forgotten

In real operations, not every action carries the same sensitivity. Sending an internal reminder, building a draft entry, posting a final entry and initiating a payment are four different levels of authority. The organization can define a permitted role, an amount limit, a second-approval requirement and a separate stop condition for each one. So the instruction "go ahead and do it" is carried out only within the boundaries already set in the organization's policy; anything outside those boundaries is clearly left for a human decision

The same boundaries apply to data. The CEO may see total payroll cost, but should not necessarily see each individual's salary. The sales director can review their own team's commission results without access to the company's full ledger. An accountant can post an entry, while changing the commission rule may be reserved for the finance director. A fast answer should not be confused with unlimited access

If a source is unavailable, a recurring run fails or two systems give conflicting numbers, the correct result is "incomplete". Arfinex should show, right then, the missing source, its effect on the answer and the action needed to complete it. That may look less appealing than a seemingly confident answer, but it is more reliable for running an organization, because the manager knows exactly which part is recorded fact and which part still needs review

AI suggests; final posting follows the rules

Conversation does not mean looser rules. AI analyzes, extracts data from documents and sources, builds drafts and proposes the path to execution. If an authorized user explicitly instructs it to proceed, or a recurring workflow has been approved in advance, the agent can take the operation through to final posting; but the calculation, the debit and credit check and the final posting are performed with deterministic, testable logic

There is no unilateral action. The level of authority comes from the user's role, the scope of the instruction, the approved rules and the organization's approval policy. If an entry is sensitive, such as an adjustment, a change to an opening balance or a payment above a limit, it waits for recorded human approval, exactly as it would if it had come in any other way

When there is no rule, Arfinex doesn't guess

Sometimes a transaction arrives for which no posting rule has been defined; for example, an account you set up for a partner sends money to a new destination for the first time. Typical software either drops it into a "miscellaneous" account or guesses

Arfinex marks the line as "held" and keeps it in the ledger with no financial effect. It shows the exact amount on the discrepancy list and asks you how it should be posted

Your answer is recorded in the decision log with the date and your exact words, and from then on it becomes a standing rule. The day that line belonged to is closed again; the earlier report for that day is not erased, and the corrected version sits next to it with a new revision number

Rules have versions, too. If you change a commission or fee rate from today, yesterday's transactions stay under the rule that was in force at their own moment

Bring your old books with you

Switching accounting software is the step most companies dread. Years of history sit in the previous software or in a folder of spreadsheets, and nobody wants to lose them or type them in again

In Arfinex, you can import historical accounting data from a spreadsheet or a supported export from your previous software. Old accounts are mapped, the original amounts and dates are carried over and the migration is checked with control totals, so the balances you had are the balances you have

That history then turns into the reports a manager needs to make decisions:

• Profit and loss
• Liquidity position
• Receivables and payables aging
• Cost trends
• Budget versus actual

Once each source is connected and approved, new events become drafts or reviewable entries according to the defined rules

Migration is not just copying rows

Each old entry is recorded at the exchange rate of its own day, not today's rate. A line that appears both in the old ledger and on the card or bank statement is recognized as a duplicate and checked with you before posting

If evidence shows that a payment was actually made from a different account or wallet, the entry goes to that real location, and the reason stays with the entry

Past fiscal years are built, and foreign-currency statements, such as a company card in lira or dollars, are imported line by line at the rate on that statement. Each batch is read once more and compared with the original file before it becomes final

Starting from an opening balance

If the full history isn't available yet, there's no need to delay getting started. Work can begin from a documented, approved opening balance

Money the owners put in to cover past costs is recorded separately in their capital account or current account. Past lines are placed behind that balance whenever they arrive, and a check confirms they add up to the same opening figure

In practice, your first day with Arfinex doesn't start from zero; it starts with a clear picture of where the company stands

The ERP implementation and multi-currency accounting service covers this area, along with sales, purchasing, inventory, projects and payroll on shared data, and a chart of accounts that can be displayed bilingually for each user. For details on rates and revaluation, see Multi-currency accounting and ERP implementation

It connects to the tools you already use

Your money data isn't in one place, and Arfinex doesn't ask you to move it all. Arfinex can connect to your CRM, crypto wallets, website or online store, payment gateways, banks, email, calendar and messaging apps, read their reports and turn them into draft entries and alerts

Example: an online store with four sources

Consider an online store that sells on its own website and on an online marketplace, with a payment gateway and a bank account. Today, someone downloads four reports every week and reconciles them by hand

When these sources are connected to Arfinex, every sale, fee, return and deposit lands in the general ledger once it is received from the source and according to the defined rules. The gateway fee is compared with the agreed rate, and the bank deposit is matched against the orders it covers

Secure connections with least privilege

The tool integration and unified automation service establishes these connections through APIs and webhooks. Every automated flow has an owner, a run log, error alerts and a way to stop it, and technical keys and secrets are kept in a secure key vault

If a system has no application programming interface (API), the connection can be made with read-only access and your own approved session. Passwords and one-time codes should not be stored in plain text, reports or ordinary workflows

Any write access is enabled only for a specific flow, with the lowest level of access needed and with event logging. Email and attachments, cloud folders and spreadsheets, work management tools, code repositories and website analytics tools are connected on the same least-privilege principle

From a photo or PDF to a draft entry

A large share of financial paperwork still arrives as paper or PDF: receipts, supplier invoices, bank statements. Arfinex reads them

Take a photo of a receipt or upload a file, and a draft financial entry is created with the date, amount, counterparty and a suggested category. The original document stays attached as evidence, and final posting happens after review and according to the rules

Upload a PDF bank statement and each line becomes a draft entry. Whatever matches existing invoices and payments is marked, and the rest is listed for review. That way, the finance team's work focuses more on reviewing the remaining items than on retyping lines

A statement that a partner or exchange sends as a photo over a messaging app is read too, but until it is matched against an independent source, it is labelled "declared", not "verified"

Core modules

Beyond these everyday capabilities, Arfinex offers a set of back-office services. The list of Arfinex services groups them into one financial core and five operational layers. For the big picture of this architecture, read What is a financial operating system?

One core, modules you can activate

The core of Arfinex is shared across all deployments, but each organization has its own separate environment, data and access. The platform administrator activates only the purchased modules for each organization, and an inactive module does not appear in users' menus or dashboards

The organization's senior administrator then decides which modules, reports or actions each colleague can access

This model lets an organization start with exactly what it needs today. Later, it can add accounting, treasury, CRM, HR, contracts or specialized agents without building a separate system

Activating, renewing and suspending modules is managed from the central subscription panel, but each organization's operational data stays in its own environment

Organization isolation and access control

Each organization is an independent space (a tenant), and in separate deployments it can have its own application site and its own database. Roles are kept separate:

• Platform administrator: manages the company and the subscription
• Organization senior administrator: sets up users and internal roles
• Operational user: sees only their own permitted menus, data and actions

Sign-in can be protected with a password and a code sent by email, an authenticator app for one-time codes, or both. Password recovery, sessions, role changes, module activation and sensitive actions are recorded in the audit trail

The approval policy is also set according to the organization's size and risk; for high-risk actions, independent approval or a compensating control can be defined. More detail is in Secure multi-tenant architecture for financial software

Daily close and account reconciliation

The daily close and account reconciliation service reads the connected money sources every night after the end of the day, turns them into entries and compares them with actual balances; total debits and total credits on the trial balance must be equal, with a difference of zero

Every difference stays on the list with an ID, a probable cause, an owner and an age, and is never closed with a manual figure. In the morning, a one-page report arrives: where the money is, and what is waiting for your decision

Financial regulators take this discipline seriously; see, for example, the UK Financial Conduct Authority's rules on client money records, accounts and reconciliations. The article Reconciliation, daily close and treasury automation also explains this process in more detail

#### Two ledgers and four controls

Two ledgers are built every night: the ledger for that day and the ledger from day one through tonight. Every number in them is a formula over dated rows, not a typed-in figure. Before publishing, four controls must be zero:

• Trial balance
• Balance sheet check
• Formula errors
• Balance of that day's entries

A snapshot of each source's balance at the moment of reading comes with the "balanced and closed" report as evidence, and the PDF version of the morning report can be archived in your own cloud folder. A file that has been delivered once is never overwritten; every correction comes as a new version. If signing in to a source isn't possible, that night is reported as "not transferred", not "closed"

#### What usually slips through

Every night, all rows visible in the source are compared with the previous night's list, not just the new rows. So a row recorded late with yesterday's date, or one whose status changed from "pending" to "completed", is caught

The day's cut-off is precise to the second, and a transaction confirmed 35 seconds before midnight lands on that same day. If a provider's balance doesn't yet reflect the latest transactions on its own list, it is read again until the balance and the list agree

Test accounts and internal company emails are also excluded from customer balances, revenue and positions, so the technical team's tests don't distort management figures

#### If a night is missed

Sometimes nobody is available at night to sign in to a source. In that case, Arfinex doesn't make up a figure and doesn't declare that night closed. The following night, each day is built separately, with its own rate and its own cut-off

The end-of-day balance for the day that wasn't read is rebuilt from that source's rows, from both directions: forward from the last snapshot before it, and backward from the next snapshot. The two paths must arrive at exactly the same number, and that number is labelled "reconstructed", not "verified"

The transfer to the accounting software follows the same order, night by night and each night at its own rate, so the result is the same as if no night had been missed

#### Closing the month and the year

Once a month or fiscal year is closed, posting to that period is locked. Reopening a closed period, changing an opening balance or changing an account that already has activity is possible only under the organization's recorded approval policy. The reason, the approver and the date stay with each change

For large organizations, this policy can mean segregation of duties and two-person approval; for a small team, a compensating control and full event logging are defined. That way, a report delivered yesterday doesn't quietly change tomorrow

Currency positions, daily rates and profit broken down

Any business that buys, sells or holds currencies or digital assets is exposed to rate changes. In deployments where the currency module and rate sources are activated, Arfinex can show the open position in each asset with its quantity, direction, average cost and unrealized profit or loss at that day's rate

The quantity that would bring the position to zero is shown next to it, together with its equivalent in local currency. That figure is only a quantity, not a recommendation about whether or when to trade. If a hedging trade closes only part of the position, the remainder stays visible and is not forced to zero

#### Reference rate and error control

The reference rate is taken every day at a fixed time from a specified source and recorded in the accounting software for each currency pair. A rate calculated from other pairs is checked against a defined deviation threshold (for example, 0.1 percent)

A rate that doesn't agree with the previous day's rate or with the calculation from other pairs, for example one that has become a thousand times larger because of an extra zero, is stopped and reported before any entry is posted with it

#### Profit, broken down

Profit isn't a single number. These components are reported separately, so it is clear where money came from and where it went:

• Commission and spread
• Withdrawal and trading fees
• Gateway fees
• Network costs
• Realized and unrealized profit and loss

Partners, counterparties and owners' money

The balance with each partner and counterparty, whether a broker, an exchange, a gateway or a supplier, is kept separately. Principal, commission and settlement are three separate events, and commission is derived from the agreed rule with a deterministic calculation

If a partner has an account on your platform from which it withdraws or sends money to its own customers, that account is shown separately from customer wallets. That way, the total owed to that partner, in any currency, remains one clear number

Money the owners put into or take out of the company is recorded in a loan current account and converted to the base currency on the same day. Wallets that belong to the company but are held by a colleague are shown next to the ledger with their own declared balance and compared every night

Nightly transfer to your accounting software

If you have separate accounting software, entries are transferred to it every night, and a night counts as closed only when the transfer is complete and checked. Every entry has a unique reference number, so even if the transfer runs again, no duplicate entry is created

Large batches, such as a month of company card statements, are first created as drafts, compared with the original file and only then made final

After the transfer, the balance of every balance sheet account in the accounting software is compared with the Arfinex ledger, in that account's own currency, and the control row must be zero. Any entry someone posted outside this path is reported separately every night

Finance colleagues can create draft entries themselves and attach the receipt or transaction ID. Every night, the evidence for each draft is checked, and if something is missing, the reason is written as a note on that same entry so the colleague knows what to do

A final entry is never edited or deleted; corrections are made only with a new reversing or transfer entry

Wallet security and fake deposit detection

In the crypto world, not every deposit is real money. A deposit the provider has flagged as suspicious or as an unverified token is not counted in the balance and is reported separately

The balances of company wallets are checked directly on the blockchain. If a wallet is targeted by "address poisoning", meaning tiny deposits from addresses crafted to look like those of real recipients, an alert is raised so nobody makes a payment by copying an address from the wallet's history

An asset and a network are two separate things. The same asset on different networks, for example USDT on TRON and on BNB Chain, is held and reconciled separately. Each network's fee, paid in that network's own currency, is recorded separately. So it is clear how much each wallet holds on each network, and what moving funds actually cost

Payments, invoicing and corporate treasury

With payments, invoicing and corporate treasury, you issue sales invoices and payment links, and the customer pays by card, bank transfer or crypto through licensed gateways and providers

Every collection is matched to its invoice and posted. Outgoing payments pass through the limits and approval policy defined by the organization, and the treasury view shows where each asset is. Arfinex itself does not hold or move funds

Identity verification, know your business and compliance

The identity verification, know your business (KYB) and compliance service connects this work to your workflow through licensed providers:

• Tiered customer identity verification
• Review of company registration documents and their beneficial owners
• Screening of politically exposed persons
• Transaction monitoring

Every decision is recorded with its documentation and the decision-maker's name. You can read the international framework for this field in the Financial Action Task Force (FATF) Recommendations

HR and payroll

With HR and payroll, the employee file, contract, attendance, leave and salary structure live in the same system as accounting. Each payroll run becomes an entry after approval, and no salary change is recorded without approval

Each person's salary can be defined in their own currency, for example some in local currency and some in USDT, and for each person it is specified which account or wallet pays them

Raises and other salary changes are recorded with an effective date, so past months' payroll stays untouched. An advance paid before the due date is tracked separately and deducted from that month's salary

Salary amounts are visible only to roles that are permitted to see them. You can start by recording only each person's base salary and paying entity, and postpone posting payroll entries until the account headings are approved

Unpaid amounts owed to colleagues, such as a cost someone paid out of their own pocket or a salary not yet settled, stay in a separate liability account until the settlement date. For an implementation guide, see Payroll accounting connected to the general ledger

CRM and a 360-degree customer view

The CRM and 360-degree customer view service brings each customer's journey together in one view. Follow-ups respect customer consent and sending limits, and each customer receives the message suited to their own stage, not a mass message

The customer funnel is measured from visit to sign-up, identity verification, first deposit, first trade and repeat activity, and every stage where customers get stuck is visible as a number. How this funnel connects to commission and revenue is covered in Revenue operations: connecting CRM, sales and commission to the general ledger

AI agents and the decision log

In the AI agents and decision log service, specialized agents for daily close, reconciliation, treasury, management reporting and other work find exceptions and propose actions

The agents analyze, build drafts and make suggestions. They can also carry out defined operations and post entries on the explicit instruction of an authorized user or within a pre-approved workflow. Outside that scope, they do not post entries or move money on their own; sensitive actions proceed according to the organization's approval policy, and the final decision rests with your people

#### Beyond the finance office

The agents don't just read the finance ledger. They compare work management tools against real evidence and find cases like these:

• A task marked "done" that has no code, output or evidence behind it
• Dozens of tasks closed together within a few seconds
• A task that has been closed while the bug itself is still visible in the product

In the code repository, they flag merges that the author approved without a second reviewer and automated tests. In website and app analytics, they mark a button users keep clicking that doesn't work, or a key event that hasn't been recorded for weeks

They also compare product designs with the approved rules, and if there is a better way, they build their proposal separately, without touching the designer's original design

#### Findings with sources and confidence levels

Every finding comes with its source, date and confidence level, and facts, inferences, suggestions and unverified items are written separately. When something needs you, a notification reaches your phone and email; when everything is normal, you aren't disturbed

For questions such as e-invoicing requirements, the validity of electronic signatures or the license needed in each country, the research agent answers with cited sources. That answer does not replace the opinion of a legal or tax adviser

#### Calculation with deterministic code, not AI

AI is not the authority for calculation or final posting. Totals, rates, fees, debits and credits are computed with deterministic, testable code

Data goes only to AI providers you have approved yourself. Their keys stay in a secure key vault, and each month's usage has a cap; crossing it stops the work or leaves it waiting for your approval. For more detail, read AI financial reporting with human approval

Other services

Arfinex also offers these services, each with its own page:

• Group consolidated reporting and management scorecard: a separate ledger for each company and a group total with intercompany transactions eliminated, with the source and status of every number
• Contracts and e-signature: contracts from approved templates, signing with a one-time code and recording of the time, device and document hash, and tracking of obligations until the contract ends. The legal validity of a signature depends on the law of your country
• Corporate records and multi-company legal documents: a separate file for each group company, with registration documents, licenses and reminders before each renewal
• Performance evaluation based on real work: each person is evaluated on the evidence of their work, not on the number of tasks closed. Disciplinary decisions are never automated
• CEO and meetings assistant agent: commitments, messages and decisions in one follow-up list with an owner and a deadline, and draft replies in the executive's voice that are never sent without their approval
• Accountable marketing and content: from ad spend to real events and revenue, with acquisition cost and return for each channel, and a content risk review before publishing
• Sales team, calls and rule-based commission: commission from revenue verified in the general ledger, with a versioned rule and the organization's approval policy before payment
• Customer support: support channels in one queue with defined service levels, and every financial request linked to that customer's financial record
• Live monitoring and actionable alerts: services, gateways, domains, bills, money queues and suspicious sign-ins, with a severity and a suggested action for each alert
• Technical governance, security and access: code merges only with a second reviewer, the least access each person needs, and backups that count as valid only after a successful restore test

Outputs in the format your team reads

Reports are produced in your team's language, and Persian and Arabic reports are built with the correct right-to-left direction; each currency has its own fixed precision. The same data can be a spreadsheet with live formulas, a print-ready PDF, a web page with charts, a Word document, a PowerPoint presentation or a shared cloud sheet

In deployments where the report engine's versioning and archiving policy is enabled, every output has a specific version, so past reports can be rebuilt and reviewed with the sources and rules of their own period

Each currency's display precision follows that asset's own rule; for example, USDT with 2 decimal places and bitcoin with 8, and a currency that has no fractional units in practice with none. The full value is kept in the ledger, and nothing is lost to rounding

Very small fees are combined into one entry each month, and rounding differences go to their own separate account. That way, the ledger isn't cluttered with thousands of rows worth a few cents, and the totals remain exact

How does working together start?

The work moves forward step by step:

1. Reviewing your needs
2. Company verification and signing the contract
3. Building in a test environment with synthetic or anonymized data
4. A parallel run alongside your current method, until the outputs match for several nights in a row
5. Moving to the production environment, only with your approval

Hosting, data ownership and software license

Depending on the chosen plan and contract, the system can run on managed hosting or on infrastructure approved by the organization itself

The organization's data, outputs and backups belong to that organization and can be retrieved through the supported export path and under the contract. The Arfinex product core and code remain under the Arfinex license, and custom capabilities are defined in the contract. Data ownership is therefore not the same as ownership of the software core or its code

Each company's data is kept separate, and even within a group, one company's report does not show any figure from another company without permission

If the subscription is not renewed

The subscription determines which modules and operational capabilities are active. The state of the environment after the subscription ends, the retention period and how exports are delivered should be made clear in each organization's deployment contract. The principle Arfinex proposes is to preserve the organization's ownership of its data and to prevent sudden data deletion; the grace period, read-only access, restricted operations and the export path are applied according to that contract and configuration

Frequently asked questions

Is Arfinex only for brokers and exchanges?

No. Arfinex is for businesses that deal with money: companies, online stores, agencies, startups, multi-company groups and the finance teams of organizations. Brokers, exchanges and payment gateways are among the most complex users, and Arfinex was designed with that level of detail in mind too

Does Arfinex hold or move my money?

No. Arfinex builds and provides software only, and it is not a bank, broker or custodian. Payments, asset custody, currency conversion and identity verification happen only through licensed providers

Can Arfinex post final entries?

Yes, if an authorized user explicitly instructs it to proceed, or the posting is part of a pre-approved recurring workflow. AI analyzes the data and guides the execution path, but the calculation and final posting are performed with deterministic, testable rules. Sensitive or out-of-rule actions still require recorded human approval

Can I create entries through chat?

Yes. You describe what happened in plain language, and Arfinex first prepares a balanced draft and its evidence. If your role allows it and there is an explicit instruction or a pre-approved workflow, the final posting is also performed with testable rules; sensitive items, items above a limit or items without evidence wait for recorded human approval

What happens to my historical accounting data?

You import it from a spreadsheet or a supported export from your previous software. The migration is checked with control totals, and management reports are built from it. If the full history isn't ready yet, you can start from a documented opening balance and add past lines later

Can it read bank statements and receipts?

Yes. Upload a PDF bank statement, a photo or a file, and a draft entry linked to the original document is created. Items that don't match are listed for review

Which languages does it work in?

Persian, English, Arabic and Turkish. The chart of accounts can be displayed bilingually for each user, and dates can be shown in the Solar Hijri calendar

What happens if a night's report isn't captured?

That night is not declared "closed". The following night, each day is built separately at its own rate, and the balance for the day that wasn't read is rebuilt from both directions using that source's rows and shown with the "reconstructed" label

Does Arfinex take our passwords or one-time codes?

For read-only connections, you sign in to the system yourself, and Arfinex uses the approved session or a restricted key. Passwords and one-time codes should not be recorded in reports or ordinary workflows, and connection keys stay in a secure vault. If a specific flow needs write access, its scope is limited, logged and revocable

Do we have to buy every module from the start?

No. Only the modules your organization needs are activated, and only those appear in authorized users' menus and dashboards. Later, you can add another module to the same environment or deactivate one

If the subscription isn't renewed, what happens to the data?

How the environment behaves after the subscription ends, the retention period and how exports are delivered should be specified in the deployment contract. The principle Arfinex proposes is that data ownership stays with the organization and ending a subscription does not lead to sudden data deletion; the details of the grace period, read-only access and exports depend on that customer's contract and configuration

Does owning the data mean owning the software?

No. The organization's data, outputs and backups belong to that organization, but the Arfinex product core and code remain under the Arfinex license

What if a transaction arrives with no rule defined for it?

It is "held" with no financial effect and stays on the discrepancy list with its exact amount until you decide. Your decision is recorded with the date and becomes a rule from then on

Can a posted entry be edited?

No. Corrections are made only with a new reversing or transfer entry, with approval, so the full trail remains. A closed month or year is also locked and can be reopened only under the organization's recorded approval policy

Can salaries be paid in different currencies?

Yes. The salary currency and the account or wallet each person is paid from are defined separately for each person, and salary amounts are visible only to permitted roles

How do I know a number in a report is correct?

Each number shows its source and reliability label, the zero controls have been passed before publishing, and a snapshot of the source at the moment of reading is attached to the report

Does Arfinex tell me what to buy or sell?

No. It only shows the quantity that would bring an open position to zero. The decision about whether and when to trade is yours

Can monthly work be repeated without defining it again?

Yes, if the workflow's source, rule, owner, authority limit and stop conditions have been approved once. Each monthly run has its own version and report, and items outside the rules or without evidence stop so that an authorized owner can decide

How is it determined which employee call led to a customer deposit?

The call log, the employee list, the customer record and the verified deposits are linked with reliable identifiers, and the organization's versioned rule defines the attribution method. An ambiguous link is not guessed; it stays for human review. After approval, the commission and the expense entry are built from those documented collections

Can I instantly compare a cost from three years ago with this year?

Yes, if that period's data has been imported or read from the source. The answer should show the period, the currency, the underlying entries and the reliability status of each number. If part of the history isn't available, that part is reported as unknown, and Arfinex does not fill the gap with an estimate

Talk to us

If you want to see exactly where your own business's money goes, use the Arfinex contact page to introduce one real workflow, its data sources and its authority boundaries for review