Yasa Midas brings invoices, customers, products and billing history into one workspace. Start with a draft, review the details and follow the record through its later stages. For ongoing services, recurring schedules help organise the next billing cycle, while an optional Hercules connection brings selected completed work into invoice preparation.
For a small business, the benefit is a clearer view of the work behind the invoice and what happened afterward. The customer, document, payment record and delivery history belong to the same billing workflow. You can find the next action without rebuilding that context from separate spreadsheets and messages.
What Yasa Midas helps you organise
The service combines customer and product records with invoice preparation, PDFs, payment tracking, recurring billing and reports. It also provides supported estimates, delivery notes, customer statements and document exports. The available controls depend on your workspace permissions and the document’s type and status.
You can use Midas independently. Hercules is an optional project connection, and access to the private Nexus infrastructure panel is not required. The Midas service introduction explains the starting point. Our Yasa Ecosystem overview places billing alongside the other services.
First, check the active business workspace and let its records finish loading. Account provides shared identity and personal preferences, while the billing workspace keeps the relevant business records and permissions. If a list appears empty, inspect the workspace and filters before creating a duplicate record.
Build reliable customer and product records
Save reusable details where they belong. A customer record supports the billing identity and contact information; product records help prepare the items you use repeatedly. Search the existing directory before adding a customer, then check names, addresses, currencies and prices against the actual business information.
For example, a maintenance business might reuse a customer and a service item each month. That saves repeated entry, but the invoice still needs a review of the period, quantity, agreed price and tax treatment. A useful default reduces typing; it does not replace the agreement with the customer.
The customers and products guide describes the current controls. Meanwhile, the company settings guide separates business billing information from personal Account preferences. Changing a display preference does not rewrite an existing invoice.
Prepare and review an invoice in Yasa Midas
Create a draft for the intended customer and describe the work clearly. Next, review quantities, unit prices, currency, dates and tax treatment. Check the seller and customer details, then inspect the totals. Save the draft and open its preview or PDF before taking the next billing action.
Think of the review from the recipient’s perspective. Can they recognise the service and period? Do the line descriptions match the agreed work? Are the payment details and relevant references clear? For a project invoice, retain enough context to connect the document to the accepted delivery.
The invoice preparation guide distinguishes saving a draft from issuing, delivering and receiving payment. This makes the workflow easier to follow: finish the preparation first, inspect its saved state, and then use the separate action appropriate to the document.
Choose the right document and presentation
Some work begins with an estimate or needs a delivery note. These are separate documents with their own status. Where conversion is supported, Create invoice produces an editable invoice draft. Review that draft before approval or sending, and open the existing linked invoice if conversion has already happened.
The estimates and delivery notes guide explains this route. Record an estimate’s acceptance only when the business confirmation exists. Similarly, choose the permitted document action for its current state rather than recreating it to work around an unavailable control.
Presentation also matters. Eligible drafts offer document templates, visible fields, accent colour and logo choices. Save the design and inspect the actual PDF for readable information and correct amounts. The document layout guide covers the available options; changing a layout is separate from correcting an issued invoice.
Connect completed work from Hercules
When a team plans its work in Hercules, selected eligible completed billable tasks can move into Midas invoice preparation. This keeps the project context closer to the billing step. Our Hercules projects and collaboration guide explains tasks, estimates and the handoff from the project side.
First, check the project’s linked customer and billing defaults. Then review the exact selected tasks in the handoff preview and choose the intended customer and draft. Finally, open the resulting invoice in Midas and check its contents before any separate issue or delivery action.
An hour estimate in Hercules expresses planned effort, rather than proving actual time worked. Therefore, agree the billing basis and verify the work you intend to invoice. The shared account helps you move between apps, while each app still applies its own workspace access. A project invitation does not grant another company’s invoices.
Make recurring billing in Yasa Midas a reviewed workflow
For ongoing services, Yasa Midas can use a saved eligible invoice as a recurring template. Review the customer, items, prices and currency first. Next, choose the frequency, next invoice date and active state. New schedules create drafts for review by default, with separate automatic approval and email modes where offered.
Choose automation deliberately. Review the recipient and authorise the intended automatic actions when selecting them. Foreign-currency schedules create drafts for exchange-rate review. After saving, reopen the schedule and check its mode, next date and last generated invoice. The original template remains a separate record.
If the service changes, update the template and schedule as appropriate. Pause stops future generation; before resuming, review the next date because missed dates may be processed. The recurring invoice guide explains these choices and the controls available to authorised administrators.
Follow delivery and payment outcomes
An invoice record helps answer several questions: is it still a draft, has it been issued, what delivery outcome was recorded, and what payment remains? Inspect the document’s details and history alongside its list status. These records make the next action more specific than a general “sent” or “done” label.
Before sending an invoice or reminder, check the recipients, message, attachments and current balance. Then inspect the recorded delivery outcome. A queued, accepted or failed message needs a different response. The delivery and reminders guide also explains why an uncertain send should be reconciled before retrying.
Record a received payment using the actual amount, currency and date supported by the evidence. Next, check the invoice’s remaining balance and payment history. The payment recording guide covers this step. Recording a payment documents the outcome; it does not move money between bank accounts. However, online invoice payments for Yasa Midas are not currently available through Yasa Pay.
Bank matching offers another supported route: import a statement in the displayed CSV format, inspect the imported transactions and confirm a match to the intended eligible invoice. Check suggested matches against the actual transaction. The bank matching guide explains imports and reversals; this feature does not establish a live bank connection.
Use reports, statements and exports with clear context
Search, status categories and filters help find the invoices you need. Reports add a selected period, date basis and available customer, currency or status filters. Before using a downloaded CSV, XLSX or PDF, inspect its scope and contents. In particular, keep different currencies distinct when interpreting totals.
Receivables shows recorded balances as of a selected date. A customer statement presents opening balance, movements and closing balance for a date range. Consequently, customer identity, dates and currency matter as much as the displayed total. The receivables and statements guide explains the views and any historical uncertainty warnings.
For retained records, distinguish a selected document bundle from a broader workspace export. Read the archive manifest and any unavailable-document explanations, and keep business records private. The downloads and exports guide describes the scope. An export should not be assumed to be a complete application restore image.
Keep corrections traceable
When an issued invoice needs an adjustment, begin with its original record, payments and related documents. Use the supported credit, cancellation or correction action for that state and review the amount, currency and relationship. This preserves the distinction between the original transaction and the accepted adjustment.
The credits and corrections guide explains the workflow. A credit note and an actual refund are separate outcomes. If a save, handoff or correction is uncertain, inspect the current record before repeating the action, so the history remains understandable.
Start with a billing cycle you can follow
Begin with the correct workspace, one checked customer record and a reviewed draft. Follow that invoice through the appropriate delivery and payment-record steps. Then add reusable products, recurring schedules or the Hercules connection where they make the next cycle easier.
Yasa Midas is currently free to use with no subscription fee, according to its public introduction. This describes the current offer rather than a permanent pricing promise. The public Midas help guides provide the current product steps as you explore the service.
If your team wants a clearer path from agreed work to invoice preparation, contact Yasa. Describe the service you bill for, who reviews the work and where the current process becomes difficult. That gives a practical starting point for choosing a manageable workflow.
