Apps: SolaProjects + SolaCount. Outcome: bill reviewed project time once, post the invoice, collect the customer's payment, and understand what project reports do and do not show.
#The situation
Palm Grove Furnishings LLC (AED base currency) also runs an interior fit-out service. For customer Bayside Café it runs the project "Bayside Café fit-out". Project manager Karim Aziz and site fitter Yousef Nasser log time on 5-7 October 2026. Mona Fares reviews the time, and accountant Layla Haddad invoices it and records the payment.
Assumptions: AED everywhere, no VAT and no discount on this invoice, no customer approval step, and the project's rates come from a rate card (below). VAT is added in SolaCount when Layla reviews the draft.
This case extends the shorter three-hour example. It is a separate practice case with its own opening position: do not enter both.
#Desired result
- Three approved time entries are billed once, on one SolaCount invoice of AED 687.50 (before any VAT).
- The invoice is posted, then paid, in SolaCount.
- Everyone understands that the time is not sent to payroll and that labour cost is a separate figure from the invoice.
#Before you start
| Item | Needed |
|---|---|
| Organization | SolaProjects and SolaCount connected; the organization setting that lets SolaProjects create finance documents is on (otherwise Billing shows "Creating finance documents from SolaProjects is turned off for this organization. Existing invoices and billed time are unchanged."). |
| Project | Customer Bayside Café set on the project; time logging on. |
| Rate card | A card in AED applied to the members (see step 1). |
| People | Karim and Yousef are project members; Mona Fares can use Time Approval; Layla has the finance permission to create invoices (project membership alone is not enough) and to post invoices and payments. |
Rate card used in this case (billing rate / cost rate, AED per hour):
| Role | Billing rate | Cost rate |
|---|---|---|
| Manager (Karim) | 95.00 | 55.00 |
| Member (Yousef) | 60.00 | 35.00 |
#Workflow overview
| Step | App | Owns |
|---|---|---|
| Rates, logging time, submit, approve, optional customer approval | SolaProjects | Hours, the hourly rate stored on each entry, approval status, billing status. |
| Create draft invoice | SolaProjects writes a draft into the shared SolaCount invoice tables | One draft invoice with one line per entry. |
| Review, tax, post, receive payment | SolaCount | Invoice, accounting and payment. |
| Payroll for Yousef and Karim | SolaHR | Not connected to project time (see App handoffs). |
#Exact steps
- In SolaProjects open the project, then Overview, the Finance section, Rate cards (project owners and managers only). Create the card with Template name, Billing currency AED and the tiers above (Billing rate and Cost rate per Role), click Create rate card, then apply it under Apply to matching roles with an Effective from date on or before 5 October. Without a rate an entry never reaches Billing: it stays Unbilled.
- Each member opens Time, clicks Log time, enters the date, hours and minutes, task, notes, keeps Billable ticked and leaves Rate source as Auto (the server uses the member rate, then the project default). Log:
- 5 Oct, Karim, "Site survey and design review": 2 h 30 min
- 6 Oct, Yousef, "Install counter panels": 6 h
- 7 Oct, Yousef, "Install counter panels": 1 h 30 min The Time screen shows durations and statuses only, no money. The rate is stored on each entry when it is saved, so changing a rate card later does not reprice entries already logged.
- Each member clicks Submit on their entries.
- Mona Fares opens Time Approval, reviews each row and clicks Approve (a member cannot approve their own entry unless allowed to self-approve; Reject requires a Reason). If the project requires customer approval, entries first show Pending customer approval and wait for Bayside Café's secure link to be approved; see Customer Approval. Only then do they reach Billing.
- Layla opens Billing. In Ready to bill the three rows show amounts 237.50, 360.00 and 90.00 and Ready amount shows AED 687.50. She ticks all three rows; Selected time shows 10 h.
- She clicks Create draft invoice (3) and confirms. A message gives the invoice number (format SP-date-time-code) and a link to SolaCount. The entries leave Ready to bill and appear under Draft invoice batches, where the status shows Draft and Unbill is offered.
- In SolaCount open the draft. It has customer Bayside Café, the project, today's date as invoice date (not the work dates), currency AED and three lines with unit "hours": quantity 2.5 at 95, 6 at 60 and 1.5 at 60. The subtotal is AED 687.50 and tax is 0. Draft lines linked to time cannot be edited for quantity, price or project; use Unbill in SolaProjects first if a correction is needed. Layla adds VAT if applicable, checks accounts, dates and custom fields, then clicks Post (see Invoices).
- When Bayside Café pays, Layla opens the posted invoice, clicks Record a payment, allocates the amount to this invoice and clicks Post twice as in Payments. Case: first payment AED 400.00, then AED 287.50.
- Back in SolaProjects open Billing. Under Draft invoice batches the batch row has an Invoice column (a # followed by SolaCount's internal record number, not the SP- invoice number) and a Status badge that is read from SolaCount each time the tab loads, so reload to see a change. After posting it reads Unpaid; after the first payment of 400.00 it reads Partially Paid; after the second it reads Paid (English interface; in other languages the Unpaid and Paid labels are translated, and Partially Paid may still appear in English). The entries stay Billed throughout, and the badge shows only a status, never an amount: check the balance in SolaCount.
#App handoffs
| Trigger / source to destination | Type | What transfers | Remaining review / posting | Effect timing | How to verify | Before retrying |
|---|---|---|---|---|---|---|
| Create draft invoice in Billing to SolaCount invoice | User-triggered | Draft invoice with customer, project, currency, notes, one line per entry (task, date, member as description; hours as quantity; stored rate; link to the entry). Entries become Billed and locked. | Tax, accounts, dates, custom fields, any invoice approval, posting. | Immediate and in one transaction; no ledger entry, no customer balance. A second billing of an entry is refused (row lock, status check, unique link on the invoice line). | Invoice number in the message; Draft invoice batches; the invoice in SolaCount. | Do not repeat if the success message appeared; look for the batch first. |
| Posting the invoice in SolaCount | User-triggered (SolaCount) | Nothing is pushed. | Layla posts. | Posting writes the journal and the customer receivable. | Invoice status Posted in SolaCount. | Check the status; do not create a second invoice for the same time. |
| Payment in SolaCount to SolaProjects Billing | Not a transfer | Nothing is pushed or sent back, and the time entries keep status Billed. SolaProjects reads SolaCount's data when a page loads: the Billing tab reads the invoice status (Unpaid, Partially Paid or Paid) and the project Reports tab reads payments allocated to the project's invoices (Collected (posted payments), Amount due (incl. tax), listed per currency). | Payment is recorded and allocated in SolaCount only. | Customer balance changes when the payment is posted; SolaProjects shows it the next time the page loads. | Invoice status and Balance Due in SolaCount. | Do not look for a Paid flag on the time entries. SolaProjects cannot set a paid or posted status: on a project document in the Finance tab use Record payment in SolaCount (or Post in SolaCount for a draft), which opens SolaCount, where the payment is allocated and journaled. The project Reports tab shows Collected (posted payments) and Amount due (incl. tax) per currency. |
| Delete the draft invoice or a draft line in SolaCount | Automatic (SolaCount code) | Linked entries are released back to Ready to bill. | Rebill if needed. | Draft only; posted, sent or paid invoices are never auto-unbilled. | Entries reappear in Ready to bill. | After a posted invoice, use a credit note in SolaCount; Unbill refuses non-draft invoices. |
| Project time to SolaHR payroll | None | None. | None. | Payroll is a separate SolaHR run. | Not applicable. | Nothing to retry. |
| Project time to SolaCount accounting cost | None | Labour cost is an estimate kept on the time entry (hours times cost rate); no journal entry is created. | Cost recognition would need a separate cost document or journal. | None. | Not applicable. | Not applicable. |
#Check your result
| Check | Calculation | AED |
|---|---|---|
| Karim, 5 Oct | 2.5 h x 95.00 | 237.50 |
| Yousef, 6 Oct | 6 h x 60.00 | 360.00 |
| Yousef, 7 Oct | 1.5 h x 60.00 | 90.00 |
| Invoice subtotal and total (no VAT) | 237.50 + 360.00 + 90.00 | 687.50 |
| Hours selected | 2.5 + 6 + 1.5 | 10 h |
| Estimated labour cost | 2.5 x 55.00 + 7.5 x 35.00 = 137.50 + 262.50 | 400.00 |
| Indicative margin on labour only | 687.50 - 400.00 | 287.50 (41.8%) |
| Balance after first payment | 687.50 - 400.00 | 287.50 |
| Balance after second payment | 287.50 - 287.50 | 0.00 |
| Stage | Ready to bill hours | Invoice | Customer balance |
|---|---|---|---|
| Approved | 10 | none | 0.00 |
| Draft created | 0 | Draft 687.50 | 0.00 |
| Posted | 0 | Posted 687.50 | 687.50 |
| Fully paid | 0 | Paid | 0.00 |
What project reporting shows (see Project profitability): the SolaCount Project profitability page lists Currency, Revenue, Cost, Profit and Margin from posted project-tagged journal lines only, so a draft invoice adds nothing and the labour estimate of AED 400.00 is not in those figures (the page states that unposted labour estimates are not allocated). The estimate appears in the Timesheet reports (Labor Cost, and Profit in the Timesheet Profitability Summary, which is billable amount less estimated labour cost) and in the Projects Cost Summary. The budget control report also adds approved time at cost rates to its labour category as an actual, so it mixes posted spending with that estimate. Do not equate 287.50 with accounting profit; supplier bills and expenses linked to the project are separate costs.
#Common variations
- Rejected time: returns to the member with the reason; correct, Submit again, approve again.
- Customer approval required: entries wait as Pending customer approval; a customer rejection sends them back to Unbilled.
- Mixed currencies: entries in more than one billing currency cannot be selected together; bill each currency separately.
- Missing rate: the entry stays Unbilled; add a rate card or member rate, then log or edit the entry again.
- Partial billing: tick only some rows; the others stay in Ready to bill.
- Error in a draft: use Unbill, correct, then rebill. After posting, use a credit note.
#Mistakes to avoid
- Creating a manual invoice for hours already in a batch.
- Editing time after it is billed to change a posted invoice.
- Treating Billed as paid: it means the entry is on an invoice, possibly still a draft.
- Expecting the invoice date to follow the work date: it is the day the draft was created.
- Expecting approved project time to pay Yousef or Karim: SolaHR payroll is separate, and no code path links the two.
- Reading the invoice total as project profit.