SolaHR can send its accounting journals to SolaCount automatically: payroll posting and payment, early overtime payments, and end-of-service settlements and their payments. Nothing is sent until you turn delivery on. A journal that was delivered is never changed afterwards; a correction is sent as a reversal.
Use it when your books are kept in SolaCount and you want payroll costs, payables and payments recorded there without typing journals by hand.
#Where to find it
| Screen | How to open it | URL |
|---|---|---|
| Integration settings | Sidebar Payroll & Compensation → Payroll Settings, card Accounting integration (SolaCount) | /payroll-settings |
| Delivery for one payroll run | Open the run in Payroll; card Accounting delivery (SolaCount) (approved, locked, closed or paid runs) | /payroll/{id} |
#Plans you need
Both apps must be on Premium or higher:
| App | Plans that include the integration | Feature |
|---|---|---|
| SolaHR | Premium, Enterprise | SolaCount integration (hr.accounting_integration) |
| SolaCount | Premium, Advanced, Enterprise | SolaHR integration (integrations.solahr) |
- This covers payroll, advances, overtime paid early, end-of-service settlements and employee claims.
- It is separate from SolaCount's developer API access: the API Integration feature and its daily request limit are not needed.
- If SolaHR's plan is lower, the card says "Upgrade SolaHR to Premium or Enterprise". If SolaCount's plan is lower, the connection test says "Upgrade SolaCount to Premium, Advanced or Enterprise".
#After a downgrade
- Nothing already received is hidden or deleted: SolaCount keeps the entries and claims, and each payroll run in SolaHR keeps its delivery history. Obligations already recorded (payroll payable, overpayments, advances, settlements) are kept through plan changes and are settled in order.
- New payroll accruals, overtime payouts, settlements, advance payouts and new claims are not sent. They wait in SolaHR with the reason shown and go out after the upgrade.
- Payments, payment returns and reversals of entries SolaCount already holds still go through, so nothing owed is left unpaid. Claims SolaCount already holds are still reviewed and paid in SolaCount, and their status keeps syncing.
- A repeated delivery of an entry SolaCount already accepted returns the same result and creates nothing new.
If the card says "The database update for this feature is pending.", the update has not reached your workspace yet.
#Who can do what
| Action | Permission |
|---|---|
| Connect, test, pause, resume, renew the key, disconnect | The organization owner, or a user granted Connect and manage the SolaCount connection (hr.integrations.connect). The same person also needs the matching permission in SolaCount (Connect SolaHR, employee_finance.connect). |
| See a run's delivery and reconciliation | View payroll runs (hr.payroll.view) |
| Retry a failed event | Approve payroll runs (hr.payroll.approve) |
#Set it up
The connection is self-service. There are no keys, IDs or addresses to copy, and nothing to run on a server. You can start from either app:
- In SolaHR: Payroll & Compensation → Payroll Settings, card Connect SolaCount.
- In SolaCount: Employee Finance → Connect SolaHR.
- Open the card. SolaHR finds your organization's SolaCount workspace by itself and checks that both belong to the same organization.
- If a plan is too low, the card names the app to upgrade (Upgrade SolaHR or Upgrade SolaCount). Nothing is upgraded automatically.
- Review the accounts. Each SolaHR role (salaries, net salaries payable, insurance, tax, advances, cash or bank and so on) needs a SolaCount account. Suggestions are marked; change any of them. If an account is missing, click Create in SolaCount. Required roles must be chosen; optional roles can stay empty.
- Choose Send entries dated from. Entries dated earlier are never sent, and history is not imported.
- Optional: tick Send employee claims to SolaCount and choose the claims payable account.
- Click Connect. SolaHR and SolaCount create and exchange a secure key between themselves, then run a real connection test. The card shows Connected once the test passes. Untick Start sending now to connect first and start sending later.
#Connection states
| State | Meaning |
|---|---|
| Not connected | Nothing set up yet. Review the accounts and click Connect. |
| Needs review | The connection works, but a required account or the start date is missing. Choose them and save. |
| Connected | Entries are sent and the last test passed. |
| Paused | The connection works but nothing is sent; entries wait in SolaHR. |
| Upgrade needed | One app's plan is below Premium; the card names it. |
| Permission needed | You lack the connect permission in the app the card names. |
| Needs attention | The last check failed. Click Test connection. |
#Manage the connection
- Test connection runs a real signed check with SolaCount.
- Pause sending / Resume sending stop and restart delivery. Entries SolaCount already received stay there.
- Renew connection key replaces the key and tests it straight away; sending continues without interruption.
- Disconnect stops sending and removes SolaCount access. Entries already received stay in SolaCount, and your account choices are kept for a later reconnect.
The Technical details card shows the connection status read-only; keys are never displayed.
#Account guide
Each account on the card shows its state, a one-line purpose and a How this works section: account type, when it is used, an example, what changes the balance, what happens if it is left empty, and when a separate account helps. SolaHR and SolaCount show the same guidance.
| State | Meaning |
|---|---|
| Configured | Saved and valid; used for new entries. |
| Suggested | Proposed by SolaCount, awaiting your confirmation; saved when you connect or save. |
| Uses default | No separate account: "Uses default account: 6101 Salaries Expense". |
| Not used yet | Your SolaHR data does not use it yet; the card says which operation needs it first. |
| Required now | Choose or create an account; the named entries cannot be sent until then. |
| Not used | No SolaCount entry uses it today; safe to leave empty. |
| Account | Type | Required | If left empty |
|---|---|---|---|
| Salary expense | Expense | Always | Payroll entries cannot be sent. |
| Net salaries payable | Liability | Always | Payroll entries cannot be sent. |
| Cash or bank | Asset | Always (never chosen for you) | Payment entries cannot be sent. |
| Insurance payable | Liability | When payroll includes social insurance | The entry waits. |
| Income tax payable | Liability | When payroll includes income tax | The entry waits. |
| Employee advances receivable | Asset | When employees have advances | The entry waits. |
| Overtime payments clearing | Liability or asset | When overtime is paid before payroll | The entry waits. |
| Deductions withheld for others | Liability (or asset for a company loan) | When payroll includes benefit, statutory or loan-repayment deductions | The entry waits; never the salary account. |
| Allowances, overtime, employer insurance expense | Expense | Not required (default account) | Uses salary expense. |
| Penalties and pay deductions | Income or expense | Not required (default account) | Reduces salary expense. |
| End-of-service expense | Expense | Not required (default account) | Uses salary expense. |
| Settlements payable | Liability | Not required (default account) | Uses net salaries payable. |
| Employee receivable (overpayments) | Asset | Before reversing a paid run that paid someone | The reversal is refused until it is chosen. |
| Rounding differences | Expense or income | Only when an entry has a rounding difference | That entry waits; entries without a difference never need it. |
| Advances opening balance offset | Equity, liability or asset | Only for a historical advances opening entry | Not used otherwise. |
#Prepare accounts for all supported workflows
What is ready lists every workflow (payroll, payments, insurance, tax, advances, overtime paid before payroll, withheld deductions, settlements, reversing a paid run, rounding, claims, historical advances) as ready, or with the accounts it still needs.
Complete setup is the default. Accounts you already have are reused and your saved choices stay. Every account a supported workflow needs but your chart lacks is shown as Will be created when confirmed, with its code, name and type; pick an existing account instead if you prefer. Choose the bank or cash account (never chosen for you) and the start date, then click Prepare and connect (Prepare and save when already connected). That one confirmation creates the listed accounts, saves the complete mapping in SolaHR and SolaCount, tests the connection and starts sending if you asked. It reports success only after both apps confirm the saved settings; if a step fails, the message names it and you can simply try again, nothing is created twice. No balances, journal entries or opening entries are created. Untick Complete setup for a minimal setup; the card lists the workflows that will not be ready.
#Currency and readiness
Entries are posted in SolaHR's payroll currency, which is also the entry's base currency in SolaCount. The SolaHR payroll currency must therefore be the same as the organization's base currency in SolaCount. Payroll lines converted from another currency are not sent, and nothing is ever posted at an exchange rate of 1. Different currencies would need a separate conversion design that is not available.
Both apps show the same readiness line, for example "Connection works · not ready to post payroll" (or "Connection not working" when the test fails), followed only by what blocks posting. A working connection and readiness to post payroll are separate:
| Check | Not ready when |
|---|---|
| Subscription | Either plan does not include the integration. |
| Permission | You lack the connection permission in either app. |
| Currency | The payroll currency differs from SolaCount's base currency (for example payroll USD, SolaCount AED), or records in another currency need review. |
| Credentials and connection health | Not connected, the signing keys differ or the last test failed or never ran. |
| Start date | No start date is saved. |
| Payment source | No cash or bank account is chosen for salary payments (never chosen for you). |
| Mappings | Required accounts are only suggested, not saved. |
The connection shows Connected only when every check passes. With a currency difference, connecting is refused before any account or key is created. Advances also take the payroll currency. An employee whose pay currency has no exchange rate is left out of the payroll run, see Payroll runs.
If the currencies stop matching after connecting (a currency changed in either app), payroll approval is refused with both currencies named, and entries already recorded wait with the reason currency_mismatch; they are kept and sent once, in order, after the currencies match again.
#Checks before HR actions
With the integration on, SolaHR checks the accounts an action's entry needs before:
- approving or closing a payroll run whose cost is recorded on approval,
- approving an end-of-service settlement,
- reversing a paid payroll run.
If an account is missing, the action is refused with the account's name, what it is needed for and where to choose it (Payroll settings → Connect SolaCount). Only that action is refused. Payments that already happened (salaries, overtime paid early, advances, settlement payments) are always recorded; their entry waits until the account is chosen. If an account is deactivated in SolaCount after setup, the affected entry waits with an explanation and is sent once an active account is chosen.
#Penalties versus deductions withheld for others
- Penalties and pay deductions are attendance and lateness deductions, disciplinary penalties, manual deductions and payroll adjustments. The employer keeps this money. Left empty, it reduces salary expense: the employee simply earned less. To report penalties separately, use an income account. Do not use a liability: nobody is owed this money.
- Deductions withheld for others are benefit, statutory and loan-repayment deductions. This money is owed onward, so it is posted to its own account and never reduces salary expense. Choose the payable to the provider, authority or lender; if your company gave the loan, choose that loan receivable.
#Entries that wait for an account
If you start using insurance, tax, advances, early overtime or withheld deductions after connecting, the affected entry is not sent to another account. It waits in SolaHR with the message "This entry is waiting for the … account in SolaCount". Choose the account in Connect SolaCount and the entry is sent automatically.
#Example entries
Below the accounts, Example entries (illustration only) shows how sample amounts (salary 1,000) would be posted with the accounts selected in the form, using the same rules as real entries. Nothing is created, posted or paid.
#What is sent
| Event | When |
|---|---|
| Payroll posted / Payroll reversed | A run becomes Paid / the paid run is reversed through its supported correction workflow. Approval alone does not queue the payroll-posting event. |
| Payroll paid / Payroll payment reversed | A run is marked as paid / the payment is undone. |
| Overtime paid / Overtime payment reversed | Overtime is paid early, before payroll, see Overtime. |
| Settlement posted / Settlement reversed | An end-of-service settlement is approved / reversed, see End of Service. |
| Settlement paid / Settlement payment reversed | A settlement payment is recorded / reversed. |
The salary expense in the payroll journal is the pay actually earned in the period.
A corrected payroll (a new revision of a paid run) is dated on the day of the correction, like the reversal of the revision it replaces, so the period already reported does not show both the original and the corrected figures. A payroll correction also takes back that run's advance recoveries, see Advances.
#Order of delivery
A payment, bank return, settlement payment or manual advance repayment is sent only after the entry it settles was accepted by SolaCount. Until then it waits in SolaHR ("waiting_for_original") and goes out right after, without using a retry. An advance payout and its entry are one step: if the entry is refused (for example by the plan), the advance keeps its previous status instead of being paid out with nothing sent.
#Follow a payroll run
On a finalized run, Accounting delivery (SolaCount) lists each available event with Amount, Status, Attempts, the SolaCount entry and Detail.
| Status | Meaning |
|---|---|
| Pending / Sending | Waiting in the delivery queue. |
| Delivered | Accepted by SolaCount; the entry number is shown. |
| Will retry | A temporary failure; Next attempt shows when. |
| Failed | Stopped retrying. Fix the cause (for example a wrong account id), then click Retry: "The event was put back in the delivery queue." |
| Skipped | Dated before Send events dated from, or a reversal of a journal that was never sent. Skipped events are left out of reconciliation. |
Reconciliation with SolaCount compares, per journal (payroll, payments, overtime payments, settlements, Overpayments owed back, Bank returns, Advance payout, Advance repayments, Employee claim), the SolaHR total with what was Delivered to SolaCount, what is Waiting to be sent, what is In the SolaCount ledger, and the Difference. The status is Matches, Waiting to be sent, Delivery needs attention or Accounting difference. Payroll for periods that ended before Send entries dated from is left out.
When delivery is off the card says "Delivery to SolaCount is turned off for this organization."
#Worked example
{Organization name} keeps its books in SolaCount. The owner opens Payroll Settings → Connect SolaCount, accepts the suggested accounts, creates a missing settlements payable account with Create in SolaCount, sets Send entries dated from to 1 November 2026 and clicks Connect. The card shows Connected. After November payroll is approved and salaries are actually paid, mark the run Paid. This queues both Payroll posted and Payroll paid. Check that both become Delivered with SolaCount entry references and that reconciliation shows Matches.
#Employee claims
Turn on Send employee claims to SolaCount to deliver approved expense claims to SolaCount for review, posting and payment. The switch is off by default. See Expenses for how claims, receipts and statuses work.
#Payroll accrual mode
Choose when payroll cost is recorded in SolaCount.
- When paid is the default. When the run is marked paid, both entries are sent: the cost entry, dated at the end of the pay period, and the payment entry, dated on the payment date.
- When approved sends the cost entry when the run is approved; the payment entry follows when it is paid. You choose a start date. Runs for months before that date keep the previous mode, and no run is ever sent twice.
#New account mappings
- Employee receivable (overpayments) is the asset account that holds money an employee received but was not owed, for example after a paid run is reversed.
- Advances opening balance offset is the account that balances the opening entry for advances that existed before accounting started.
#Advance accounting
Set the Advance accounting start date. From that date SolaHR sends journals for the advance payout, for suspension of an advance, and for repayments recorded by hand. Advances disbursed earlier are handled by the historical decision below.
#Historical advances
Open the historical advances reconciliation report. It lists every advance that was outstanding before the start date. A finance administrator then makes one decision for the organization, one time.
- Already booked by hand: your books already contain these advances, so nothing is sent.
- One opening entry: one journal records the total outstanding balance.
- One opening entry per advance: a separate journal for each advance.
The decision is bound to the report you reviewed. If the advances change afterwards you must review the report again. Nothing is ever sent automatically for historical advances.
#Reversing a paid payroll run
- Reversing a paid run marks it Reversed. It does not reverse the bank payment, because the money has already left the bank.
- The net pay of each employee is recorded as an overpayment, an amount owed back by the employee, in the employee receivable account.
- If an employee genuinely returns money to the bank, record the bank return on the run. This reduces the overpayment.
- Reissue a reversed run to create a new revision. Its pay first settles that run own outstanding overpayment. Overpayments from other months are never offset automatically.
#Scheduled jobs
- Delivery to SolaCount runs every 5 minutes and retries failed items.
- Status reconciliation runs every hour and fixes any claim or journal whose status was missed.
#Tips and common problems
| Problem | Cause | Fix |
|---|---|---|
| Nothing reaches SolaCount. | Delivery is off, or the events are older than the start date. | Turn delivery on; check Send events dated from. |
| Upgrade needed — "does not include the SolaHR integration" | SolaCount is below Premium, or its subscription ended. | Upgrade SolaCount to Premium, Advanced or Enterprise, or renew. |
| The card says "Upgrade SolaHR to Premium or Enterprise". | SolaHR is below Premium. | Upgrade SolaHR. |
| An entry waits with "plan_required". | One of the two plans is below Premium. | Upgrade the app named in the message; the entry is then sent automatically. |
| The card shows Needs attention. | The last check with SolaCount failed. | Click Test connection; if it keeps failing, click Renew connection key. |
| "SolaCount could not be reached right now." | A temporary network problem. | Try again in a moment. |
| Needs review after connecting. | A required account or the start date is missing. | Choose them on the card and save. |
| Claims are not reaching SolaCount. | Delivery is off, or claims are not enabled in SolaCount ("Employee claims are not enabled for this SolaCount organization"). | Turn delivery on in SolaHR and enable claims in SolaCount. |
| An event shows Failed. | SolaCount refused it, often an unmapped or wrong account. | Fix the mapping, then Retry. |
| Reconciliation shows Changed after delivery. | The run was changed after its journal was delivered. | Review the native payroll correction/reversal workflow and the actual event history with finance. Approval alone does not send a new payroll journal. |
#Related
#Business Solutions & Examples
Follow the complete business workflow for prerequisites, app handoffs, expected balances and common exceptions.