Turn Rivilė Debt Reports into a Management Tool with Power BI

In Rivilė, you produce a debt report via Servisas → Debitorinės/Kreditorinės operacijos → Kliento būklė (Service → Receivables/Payables Operations → Client Status) or Suminės skolos (Summary Debts). Before printing, check three things: the status date, the currency revaluation and the settlement status, because an error in any one of them distorts the whole picture of what is owed. If you need to take debt management to the next level, for example to see late-paying customers in real time, this data can be automated in Power BI.


In brief:

  • A debt report must be produced accurately: the status date, exchange rates and settlement statuses should all be checked before printing.
  • Debt settlement modes include manual, semi-automated and FIFO, and these must be kept clearly separate to avoid confusion.
  • The system can automate payment reminders and reconciliation statements by setting a minimum overdue amount threshold and using a dedicated system setup.
  • Costly errors most often stem from incorrect currency revaluation or settlement rules that have not been set up, so these must be checked against the documents.
  • Power BI lets you monitor the debt position automatically and visually, which is particularly useful for large companies and multi-branch structures.

Contents

How to produce the main debt reports in Rivilė

Rivilė debt reports are generated in one place, but the result depends on how you set the filters. Rivilė’s Receivables and Payables Operations module lets you view customer and supplier balances, analyse debt ageing and print a report straight away based on the criteria you choose.

The main window is opened via the menu Servisas → Debitorinės/Kreditorinės operacijos → Kliento būklė (Service → Receivables/Payables Operations → Client Status). This window produces both summary and detailed reports, depending on the format selected. The Rivilė guide states that the result is determined by two settings: the status date and the filters applied.

In practice, the sequence of steps looks like this:

  1. Open Servisas → Debitorinės/Kreditorinės operacijos → Kliento būklė.
  2. Set the status date up to which the balance is calculated. This date determines whether the report shows the current or a historical position.
  3. Choose the filters: customer or supplier, currency, specific invoice conditions.
  4. If you need an overall view without detail, print „Klientų būklė suminė (i)“ (Client Status Summary).
  5. If you need to see each invoice separately, switch to the detailed report form.
  6. Check the payment schedule if the customer pays in instalments over several due dates.

The summary report is suitable for a quick check when you need to know the total amount owed. The detailed version is useful when you need to trace a specific invoice or resolve a query with a customer about a particular payment.

Pro tip: If you are preparing the report ahead of the month-end close, always set the status date to the last day of the month rather than leaving the default of “today”. Otherwise the report will include transactions that logically belong to the next period.

How debt settlement works: manual, semi-automated and FIFO

Settlement in Rivilė means matching a debt with a payment, either against a specific document or for the full amount. The system has three fundamentally different modes, and mixing them up is the most common source of confusion in reports.

  • Manual settlement. The user chooses which payment settles which invoice. This suits cases where the customer pays quoting a specific document, or where a special arrangement is needed.
  • Semi-automated settlement. The system matches entries only when the customer, currency and document number all match. This is convenient when the payment order includes the invoice details.
  • Automated (FIFO) settlement. The Rivilė module description confirms that the automatic mode settles the oldest debts first, based on the FIFO principle, and requires a rule to be set in advance on the customer record.

FIFO settlement speeds up work with customers who pay regularly without specific references, but it needs to be reviewed manually when a customer has disputed invoices or partial payments in several currencies.

How to produce payment reminders and reconciliation statements

Reminders and reconciliation statements are produced in the same Receivables/Payables Operations module, in the customer notification list. The Rivilė guide describes the full setup, from the minimum amount through to automatic sending.

  • You can set a minimum overdue amount in the system, below which no reminder will be generated.
  • Only customers with at least one invoice above this threshold are included in the notification list.
  • In the email template you can use the variable {{clientAdditionalEmails}} so that the reminder goes not only to the main contact but also to the customer’s additional contacts.
  • Automatic sending requires a separate user with restricted permissions, a defined export template and a task scheduler, such as „Tasker“ or the „Windows“ Task Scheduler.

Pro tip: Create a dedicated system user solely for sending reminders. If you use a shared accountant login, any session interruption will halt the entire automation.

How to create payments from summary debts

Payment transactions from summary debts are created on the same principle as reports, just in a different window. The Rivilė guide on summary debts describes the exact sequence.

  1. Open Servisas → Debitorinės/Kreditorinės operacijos → Suminės skolos (Service → Receivables/Payables Operations → Summary Debts).
  2. Choose the period and the customer whose debts you want to select.
  3. Tick the required documents in the list.
  4. Click „Atsiskaitymo operacijų formavimas“ (Create Settlement Transactions) and set the transaction type to „Išmokos“ (Payments Out).
  5. If needed, tick „Naudoti mokėjimo datą“ (Use Payment Date). This setting carries the summary debt’s payment date over to the newly created payment instead of assigning today’s date.
  6. You will find the created transaction under Atsiskaitymai → Išmokos (Settlements → Payments Out).

This route is especially useful when you need to prepare a bulk payment list for several suppliers at once without creating each transaction separately.

Foreign currency debts and the most common report errors

When a customer or supplier has invoices in a currency other than the base currency, the report will be wrong until a revaluation has been run. Rivilė’s lesson on customer debt analysis notes that the revaluation must be carried out before the report is produced, not after.

The status date matters even more for foreign currency balances than for the national currency: the date chosen determines the rate at which the unpaid balance is valued. This can be monitored further with an analysis of exchange rate fluctuations, as described in the guide to currency market analysis.

  • Never adjust figures in the report itself. The Rivilė guide reminds users that corrections must go through the receivables or payables transaction documents, not through the report window.
  • Check whether a settlement rule has been set on the customer record. Without one, automatic settlement simply will not kick in.
  • Review debt ageing regularly, as a single one-off report does not show the trend.

Debt ageing should be monitored at least once a week, because an infrequent one-off check cannot catch late payers in time, according to the Rivilė ERP documentation.

The Analitika360 perspective: when Power BI complements Rivilė reports

Rivilė’s printed reports are accurate but static: you see a snapshot that has to be refreshed manually every time. That is good enough when the list of debtors is short and one accountant has time to review it every day.

Things change when there are hundreds of debts, several branches, or a dozen or more customers jostling in a single list every day. At that point, manually reviewing Rivilė reports becomes a waste of time that can be avoided. Analitika360 Power BI reports connect Rivilė data to a visual dashboard that refreshes automatically and shows at a glance which customers are the most overdue and what the overall risk is.

This solution is often used by companies working with several customer groups at once, and by restaurant chains where debts are spread across many suppliers. Implementation typically takes anywhere from a few days to a few weeks, depending on the number of data sources.

— Analitika360

Rivilė reports vs. automated debt management

If you already know how to print a client status report in Rivilė, the next logical step is to ask: how much time do you spend reviewing it every week?

Analitika360

Even without replacing Rivilė, where transactions and settlements continue to be handled, you can take the same data and turn it into a live dashboard that refreshes without anyone stepping in, doing away with manually printing the summary report and comparing figures every week. Have a look at the Power BI report examples to see what a real-time overdue customers dashboard looks like.

A demonstration is worth requesting if you manage several branches, deal with dozens of customers at once, or simply want your manager to get a view of debts without having to ask the accounts team. Get in touch for a consultation or a sample report via the solutions page and work out how much time you would save each month.

Rivilė reports vs. automated debt management — overview diagram

Sources

You will find the detailed steps in Rivilė’s debt management guide, the description of the reminder setup in the Rivilė GAMA guide, and the instructions on creating payments from summary debts. To learn more about Rivilė data analytics, visit the Analitika360 page.

Further reading

Using Rivilė?

Analitika360 builds Power BI reports straight from your Rivilė data. They refresh automatically, from €59 a month.

Rivilė reports
Analitika360 client stories

Data that helps you decide

See how companies like yours put Analitika360 reports to work in Power BI.

“
We took the standard R-Keeper report package and they tailored it to us on top of that. It all just works.
TB
Tomas B.restaurant owner
“
Twenty ready-made reports — we didn't have to work out what to ask for. Our Finvalda data is finally something you can look at. Recommended.
IM
Ingrida M.accountant
“
What we liked was that Analitika360 already had a 20-report package for Rivilė users — we didn't have to work out our requirements from scratch. We were up and running quickly, and later they adapted several reports to the specifics of our production. It saved us both time and money.
MK
Marius K.finance director
“
We are a group of companies running Rivilė, and consolidated reporting was always a headache. Analitika360 started from the standard 20-report package and then fitted it to our group structure — we now see everything in one Power BI model, and it refreshes itself.
GJ
Giedrė Jankauskaitėfinancial accountant
“
We run six restaurants on R-Keeper and had long been looking for a way to compare results across sites. The standard 20-report package covered most of what we needed, and reports specific to our group were added later.
AŠ
Andrius Š.director of a restaurant group
“
We came to them on a recommendation, and the ready-made 20-report standard for Finvalda users was a pleasant surprise straight away. Management now gets a clear financial picture every Monday, and I no longer spend days exporting data into Excel.
RP
Rasa Petrauskienėhead of accounting
“
We use Rivilė, but we never had time to build reports from scratch. The 20-report package was exactly what we needed — we had it running within a week.
VP
Vaidas P.retail chain manager
“
We have four cafés on R-Keeper and for a long time we ran them on gut feel. The Analitika360 reports showed us things we had simply never noticed. We now decide on the numbers rather than on guesswork.
LK
Laura Kazlauskienėfinance director of a café group