Monthly income check
Compares rent and household data with income statements (PDF) and reports discrepancies.
Overview
Every month, rent and household data must match the income statements. This automation exports the data, locates the statement PDF for each unit, extracts the values, and compares them against the source. Matches, discrepancies, and input issues are compiled into separate logs and emailed.
What has changed
- Eliminates repetitive manual checks
- The check is performed the same way every month
- Auditable logs show successful checks, discrepancies, and input issues
At a glance
In één oogopslag
Overzicht
Every month, rent and household data must match the income statements. This automation exports the data, locates the statement PDF for each unit, extracts the values, and compares them against the source. Matches, discrepancies, and input issues are compiled into separate logs and emailed.
Wat er verandert
- Eliminates repetitive manual checks
- The check is performed the same way every month
- Auditable logs show successful checks, discrepancies, and input issues
How it works.
What it does per property
- Determines the reporting period
- Exports rent data from Business Central
- Locates the corresponding income statement PDF for each unit in the document system
- Extracts rent, income, and household size from the PDF
- Compares the values with the source and logs discrepancies and input issues
- Emails the output files
Rules
The reporting period is the previous month, unless a date range is specified, and the month determines whether the live environment or the archive is used. Extracted values are compared with the source, and any difference or unreadable document is logged. Because the logic is fixed, the same input always yields the same result, and every run is logged.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.