Amount due by service and recipient
Before paying, check the amount for each service and who will receive it.
Residents know what they are paying for. Accountants can follow each payment.
Residents see the service and amount due in the app, then continue to the bank’s payment page to pay by card. Afterwards, they can check the result, open the electronic receipt and manage their saved cards.
Before paying, check the amount for each service and who will receive it.
Continue from the app to the bank’s payment page and follow its steps to complete a card payment.
View and manage saved cards to keep the options you want for future payments.
Check the transaction result after payment and open the receipt as evidence of the payment.
After paying by bank transfer, a resident can attach the receipt for confirmation. Arega helps read the amount, date and recipient and flag potential inconsistencies; an accountant reviews the document and approves or rejects the payment record.
Attach the bank receipt in the app so an accountant can check and record your transfer.
Pre-read receipt details help staff review a transfer without retyping all of the information.
A possible duplicate or inconsistency flag prompts staff to examine the receipt before approval.
Submitting a receipt does not itself confirm the payment; staff review it and decide whether to record it.
Check the relevant recipient’s bank details before making the transfer so the money reaches the correct account.
Track your submitted receipts and withdraw an incorrect or unnecessary submission at a permitted stage.
A submitted receipt amount can appear as awaiting bank confirmation until the payment is finally recorded.
After importing a bank statement, accountants review which property and payer each transfer has been matched to. Unrecognized and duplicate rows are checked separately, and the matching result is confirmed before payments are recorded.
Upload the bank statement and preview the incoming rows before proceeding with reconciliation.
Check the matched property and payer for each transfer so the amount reaches the appropriate account.
Review payments with an unrecognized payer or property separately and determine the correct match.
Duplicate flags help identify previously imported entries and avoid recording the same transfer twice.
Confirm the reconciliation after reviewing the matches to finalize the payment records.
Payment history distinguishes successful, pending and unconfirmed transactions and can be filtered by date or status. The same history provides access to receipts and recorded overpayments and refunds.
Use the status to see whether a payment succeeded, is still pending or has not been confirmed.
Filter by dates or transaction status to locate a particular payment in a long history.
Open and download a previous payment’s receipt whenever supporting evidence is needed.
View recorded overpayments and refunds to understand how they affect the balance.
Where automatic payments are enabled, residents can opt in, choose a payment card and set an amount limit. They retain control of the arrangement and can withdraw consent when they no longer want automatic payments.
Automatic-payment settings are available when the service has been activated for your building.
Residents must separately accept the relevant conditions and consent before automatic payments are enabled.
Choose the payment card and permitted amount limit to control the automatic-payment arrangement.
Withdraw consent in the relevant setting when you no longer want automatic payments.
Received money should be applied to the correct resident and obligation. The accountant can review allocated and unallocated amounts and resolve outstanding mismatches.
Residents can distinguish amounts due for an apartment, parking space or other property and select the relevant item.
Gather selected payments in a basket while retaining any separate payment steps needed for different recipients.
With accounting permissions, apply a recorded payment to debts using the suggested allocation or a manual adjustment.
Find payments whose amounts have not yet been fully applied to obligations in a dedicated queue.
A bank operation may need verification or further processing. Authorised finance staff can find these cases, check the bank’s response and follow the final outcome.
Review pending or unfinished payment attempts and identify those needing additional checks.
Authorised staff can recheck the bank result when the displayed status is not yet final.
With the required permission, initiate an eligible refund or bank cancellation and track its processing.
Recorded attempts and results show whether a refund has been requested, is pending or has completed.
Link a bank card for future payments and choose your preferred one. Saving a card and consenting to recurring charges are separate choices.
Add a card through the bank’s supported process so it is available for your next payment.
Choose a default card for the relevant recipient to make starting your next payment easier.
Initiate a new payment yourself using one of the available saved cards.
Remove a card you no longer use from your saved payment methods, subject to bank processing.
Recognise recurring bank-statement descriptions using saved rules. Each import still has its own review, confirmation and history.
Save a rule based on the description or counterparty to make similar rows easier to recognise on the next import.
Retain a recognised link to an apartment to reduce repeated matching work for future transfers.
Open a previous import batch to inspect its rows, matches and recorded outcome.
Where permitted, reverse an incorrect import result while retaining the action history.
Availability depends on the user’s role, enabled services and compatible equipment.