Corveek A LOYA product Features
22 features across 8 areas — each one something the product does today, written down where a buyer can check it.
Showing all 22 features.
Books that close, and reports that agree with them
Open any document and see the whole chain it belongs to, from estimate to ledger.
Estimates, orders, invoices, payments and journal entries are linked as they are created, never by re-keying. Any reader can open the chain from any step, and every document in it is shown open or locked by that reader’s own permissions — so the journey is whole without anything being disclosed.
Invoice in your client’s currency and keep your books in yours.
Every document stamps the rate it used and never re-reads it, every journal line carries both amounts, and the difference between an invoice’s rate and its payment’s is posted as a realized gain or loss rather than left in the receivable.
PPh 23 and 4(2) withholding, bukti potong, faktur pajak and e-Bupot files.
Withholding is computed on the bill line that causes it, the certificate prints in the authority’s own layout, faktur pajak serials are captured where the VAT report finds them missing, and the files for e-Bupot and Coretax are exported from the same records.
A closed month refuses new postings, so last quarter’s figures stay put.
Every posting is dated from its document and checked against the period calendar at one place in the ledger. A correction to a closed month is dated today, so closing December never traps a fix.
Match statement lines to journal lines; the difference is the signal.
Auto-match suggests and a person commits, outstanding items are listed by what to do about them, and nothing in reconciliation ever posts — a missing transaction is created through its real document.
Revenue, direct cost and overhead per unit, from the stamped ledger.
Every journal line carries its cost centre and job, stamped when it posts, so a business unit’s performance is read from the ledger itself rather than from a spreadsheet beside it.
People, time and pay in one place
Monthly runs with TER, a year-end true-up, BPJS, THR and final pay.
Attendance, unpaid leave, overtime and claims feed the run directly, the 1721-A1 and the payroll filings come from the same payslips, and net salary is paid and posted from the run.
Accrual and balances, rosters, corrections and timesheets on jobs.
Leave accrues by policy and is checked against its balance and overlaps, attendance can be corrected with a reason, and time on a job is costed into that job.
A careers page, a candidate pipeline, offer letters and onboarding.
Candidates apply from your own careers page, move through your pipeline stages and panels, and are hired into the party record they already are — nothing is copied and left to drift.
Administration, content and the approval matrix
Route a document by amount, cost centre, job and seat — never to its own author.
Bands decide which seats must sign, and a seat is a position, so a resignation is one new assignment rather than a hunt through open requests. Whoever raised a document is dropped from its own chain, and cover is handed over by the person who holds it.
Roles decided in your workspace, with record-level scope enforced on the server.
A grant says what a role may do and over which records — its own, or everyone’s — and the server enforces both on every request. Nobody can hand out authority they do not hold, and hiding a button is never what keeps a record private.
Every change, with who made it, when, from where, and the values before and after.
Every create, change and delete is recorded — including refusals — and each record shows its own history and correspondence on its page, so the question “who changed this?” is answered where it is asked.
PDFs, spreadsheets and emails wear your logo, address and footer.
One letterhead, resolved once, printed by every medium — so an invoice, a statement and the email it was sent with cannot disagree about who sent them.
Approvals, answers from clients and announcements, with email by preference.
Each person is told what concerns them, and opening a message is recorded as a receipt, so “were they told?” has an answer.
One record for every customer, supplier and person
Your counterparties sign in to see, acknowledge and answer their own documents.
A client reads its invoices and answers its quotations; a supplier acknowledges purchase orders and quotes on requests for quotation. Each sees only the documents addressed to it, field by field, and a company can apply to become a supplier from a link you send.
Every list of values, and the item master behind every line
Dated prices and costs, renameable vocabularies, imports from your files.
A price in force cannot be edited, only succeeded, so last year’s documents still explain themselves; a workspace can rename any value it shows; and a catalogue or vendor list arrives as a spreadsheet.
From estimate to sales order, with the margin in view
Cost each line from a rate card, and see planned against actual per job.
An estimate carries a cost sheet beside its price, a margin floor refuses a price that would lose money, and every purchase, bill and expense charged to the job is measured against the plan it was costed with.
Offer the client several estimates and let them choose.
A quotation is the set of estimates the client chooses between. The one they choose is the job — it is what converts to an order and an invoice, and what spend is charged to.
Spend that is decided before it is incurred
Requisition, request for quotation, compared quotes and a recorded choice.
Suppliers quote on the same lines, by email or in the portal, and the reason one was chosen over the others is kept with the order it became.
Order, receipt and bill agree before the bill can post.
A bill is matched against what was ordered and what arrived, line by line, and the goods-received-not-invoiced account is restated in your own currency at every movement.
What every module shares
Single sign-on with Google and Microsoft, two-step codes and a device list.
An address is one account whichever door it uses, two-step sign-in can be required per workspace, and a person can see every browser signed in as them and end any of them.
Belong to several workspaces and move between them without signing out.
Identity is global and roles are per workspace, so the same person can administer one organization and only read another — and tenant isolation lives in the data layer, where a query cannot forget it.
Tell us your modules and team size and we will set up a workspace to try it in — or sign in if you already have one.
