Lessorløn + Prowi

Imagine that the commission is calculated correctly in Prowi, validated by the employee himself and lands in LessorSalary without manual intermediate invoices. No copy paste. No salary errors. Only a stable process that runs on time and provides a complete overview for both finances and employees.

In this article you will get a concrete roadmap for Prowi and LessorPayroll integration via CSV. We review step by step, field mapping, governance, KPIs, examples and best practices, so you can go from Excel chaos to reliable automation in one pay cycle.

Why choose CSV as the first step?

CSV gives you fast time to value without a development project. It's flexible, transparent, and scalable from a few vendors to larger teams.

Advantages in practice:

• Quick Setup: No reliance on an API project.
• Robust Documentation: The file is your audit trail.
• Fewer errors: Amounts are approved in Prowi before export.
• Easy Scaling: The same process works for 5, 50 or 500 employees.

In short: CSV is the simple way to a stable integration between Prowi and LessorSalary.

How the process works step by step

Overview

1. compute commissions and bonuses in Prowi based on your CRM data and commission models.
2. Approve the amounts via Prowi's employee app and admin flow.
3. Export a CSV from Prowi in the agreed format.
4. Import CSV in LessorSalary, where salary types and employees are matched correctly.
5. Drive salary in LessorSalary as usual. Commissions and bonuses are now included.

The essence is simple: LessorSalary receives clean, approved numbers without manual typing.

Field mapping that works in LessorSalary

A proven setup typically looks like this:

• Employee ID or E-mail as unique employee key
• Name
• Salary species for commissions, bonuses, guarantees, deductions and corrections
• Amount in DKK with correct decimal separator
• Period e.g. 2025-09
• Department/Team as reporting field
• Notes/References e.g. “September commission, Plan A, HubSpot deals”

Type: Agree in advance precisely what types of wages in LessorSalary which is used for commission, bonus, vacation and sickness averages as well as clawbacks. Consistent payrolls yield nicer reports and fewer postings.

Authentication flow that minimizes errors

Variable salary errors often occur before the file hits the payroll system. Hence Prowi's strength lies sooner exports:

• Self-control: The employee sees the expected payout, history and corrections in Prowi.
• Automatic Logging: All changes and approvals are recorded.
• Warnings: Admin sees missing data, duplicates and unresolved absence records.
• Valori bloccati: Once the period is approved, Prowi locks the exported values.

Results: LessorSalary imports an error-free basis. You avoid reruns, manual corrections and disgruntled employees.

Security, GDPR and documentation

Data minimization and traceability

• Required fields only exported.
• Safe handling via controlled channels or direct upload.
• Audit package: Save CSV, Prowi period report and LessorSalary import log in aggregate.

Roles and Responsibilities

• Prowi is the computational engine and source of truth for variable pay.
• LessorSalary is the system of disbursement and accounting basis.
• Finance/Payroll owner import and final control.

Best practice: Describe the integration in your controller manual and attach a checklist for each pay cycle.

Setup in practice in under 60 minutes

1. Define salary types in LessorSalary for commission, bonus, vacation and sickness averages, as well as clawbacks.
2. Match employees between Prowi and LessorSalary. Use EmployeeID or Email as the key.
3. Configure export template in Prowi. Determine the separator, column order and decimal places.
4. Make a dry run on a closed test period.
5. Import in LessorSalary and vote against Prowi's period report.
6. Lock the template and document the process in the controller manual.

Pro tip: Arrange a firm cut-off date. When the Prowi period closes, export and import are exported and imported on the same day. It gives peace of mind to the salary.

Edge cases you should be aware of

Absence, vacation and illness

Prowi can calculate average commission in case of vacation and illnessso that your practices and rules are followed. Use a separate salary type in LessorSalary and clear notes in exports.

Split-deals and cross-cutting teams

Prowi automatically allocates amounts per employee. The CSV gets one line per person, same period and clear reference.

Clawbacks and Corrections

Credit notes and returns can be posted as negative lines on a dedicated paycheck. It provides a transparent track in LessorSalary and preserves fairness for the employee.

KPIs that demonstrate value

• Time spent per pay cycle: Reduce from days to hours
• Error rate in variable pay: Decrease in post-payout corrections
• Time from approved commission to payout: Shorter lead time
• Employee Satisfaction: Higher perceived transparency and fairness
• Polling Speed: Faster Closing in Finance

When the numbers move, the behavior moves. Here Prowi delivers measurable ROI.

FAQs about Prowi and LessorSalary via CSV

How do we match employees?
Choose the most secure key in your HR master. EmployeeID is robust. Email can be used if it is unique and consistent.

What types of wages should we use?
Minimum one for commission and one for bonus. Consider separate pay types for vacation and sickness averages, as well as clawbacks.

What about rounding and VAT?
Commissions and bonuses are gross amounts without VAT. Prowi exports two decimal places. LessorSalary rounds off by default.

Do we need a DPA?
Yes, Prowi provides Data Processing Agreement and Documentation. The CSV exchange follows the same security principles as other data processing.

Can we later move from CSV to a closer integration?
Yes. Start simple. Once the process is stable, you can automate further as needed.

Best practice checklist

• Define salary types in LessorSalary and document them
• Agree cut-off dates for Prowi closure and LessorWage import
• Use fixed templates in Prowi and lock column order
• Save period report, CSV, and import log as an audit package
• Target KPIs at each pay cycle and iterate the process

Next steps

Prowi and LessorPayroll integration via CSV provides you with a stable, scalable and audit-ready process for variable pay. The employee approves his figures in Prowi, finance imports one file into LessorSalary, and the salary runs on time with fewer errors and higher transparency.

Do you want to see it in your data as early as the next salary cycle?
Book a short review. We put Prowi and LessorSalary CSV up, do a dry run and document the effect with your own KPIs.

‍