Morning (Green Invoice): What It Does, Who It Fits, and What Connects to It

Morning is a cloud system for issuing invoices and running a business, still also known as Green Invoice - its own site presents itself as "Morning by Green Invoice". It issues digital invoices and receipts, manages income and expenses, clears cards, Bit and digital wallets, and obtains Israeli allocation numbers automatically through a connection to the Tax Authority.

What the system includes

According to the company's site, the division is as follows:

The sixth row became critical over the past year. Where an allocation number is required, the difference between a system that obtains it automatically and one that needs a separate action is a difference in daily working time.

How much does Morning cost?

At the time of writing (November 2026), Morning's pricing page lists four plans. Prices are per month and exclude VAT; on the annual subscription the year is paid in one payment.

The line that matters for anyone planning a connection: "automations through API, integrations and Webhooks" appears in the Best and Extra columns, and Prime includes everything in Extra. Basic does not list it. So a business that wants its website, store or CRM to issue documents through the API should price from Best, not Basic. Every plan offers a free trial; the page does not state how long it lasts.

How do allocation numbers affect the choice of system?

An allocation number is an identifier obtained from the Israel Tax Authority before issuing a tax invoice above a given threshold. Morning's site carries a notice that enforcement of the requirement began on 1 June 2026, and states the amount above which it applies. The threshold itself has been updated more than once, so the binding figure should be read from the Tax Authority page rather than from an article - and the dates confirmed there too.

What can be said clearly, and what matters for choosing a system:

• An invoice above the threshold without an allocation number affects the recipient's ability to deduct input VAT. That makes it your customer's problem, and it comes back to you.
• The process is meant to be automatic: the system calls the Tax Authority servers at issue time and receives the number.
• So the question to a vendor is not "do you support this" but "show me it happening while a document is issued".
• And you need to know the failure behaviour: if the request is rejected, is the document blocked, saved as a draft, or issued without a number.

The technical side of that flow is documented in allocation numbers for developers, and what to do when a request is rejected is in a rejected allocation number.

Who it fits, and who it fits less

It fits a sole trader who wants to issue documents and take payments from one place; a business selling online that needs an automatic invoice per transaction; a small company that wants its accountant to have access rather than files; and a nonprofit collecting donations online.

It fits less well where there is complex inventory with bills of materials, where a production floor or hourly project costing is needed, or where the business already runs an ERP that owns the documents. In those cases an invoicing system is a duplicate layer - see when to replace an ERP versus adding a calculation layer.

What does paying with Morning mean?

Paying with Morning means the customer pays through Morning itself: the company's site lists card, Bit and digital-wallet payments, with an automatic invoice per transaction. In Morning's API the same capability appears as a hosted payment form (POST /payments/form) that you send to a customer, and as saved credit-card tokens that can be charged later. The practical gain is that the payment and the document are created in one place, so there is less to reconcile between a clearing report and the invoicing system.

What can you connect to Morning through its API?

Morning's API covers documents, clients, items, suppliers, expenses and payments, and it sends webhooks for events such as document/created, payment/received and client/created. It has a sandbox with its own keys, and its access token is valid for one hour. The common uses:

• Issuing a tax invoice-receipt when a website order is paid.
• Pushing a payment back to the CRM so a salesperson sees who has paid.
• Turning an accepted quote into a document without retyping the rows.
• Keeping one client list instead of two that drift apart.

The technical detail, with endpoints and error codes, is in the Morning API automation guide, and the customer-sync side in connecting invoicing software to a CRM.

What stays with the accountant

This is the common point of confusion. An invoicing system is the source of documents, not a replacement for filing and audit:

• Filings to the authorities and professional responsibility stay with the accountant or tax adviser.
• The system gives them access and reports, which removes the manual handover of materials.
• Classifying expenses in non-trivial cases remains a professional judgement, even when the system suggests one.
• Year-end closing and annual reports are not something an invoicing system produces by itself.

What does change is the volume of work. Instead of collecting receipts at quarter end, material flows in continuously - the difference between two days of work and half an hour a month, as covered in the business, accountant and bank workflow.

Three mistakes when adopting an invoicing system

• Starting mid-year without closing the previous book. If you issued invoices in a paper book or another system, you have to decide which number to continue from and record that decision. Broken numbering is the first thing an accountant sees.
• Migrating customers without cleaning them. Importing a customer list with duplicates, wrong ID numbers or dead email addresses creates problems in every future document. Better to import less and clean.
• Not defining who issues documents. In a business with two or more staff, two people issuing in parallel produce duplicate documents for the same transaction. Permissions are not an advanced feature; they are a setup step.

The first mistake is the only one that is hard to fix after the fact, so handle it before the first document rather than after the hundredth.

What to test in a trial, not in a demo

The site offers a trial period; use it to test precisely these:

1. Issue a real invoice above the threshold and watch the allocation number come back.
2. Issue a credit note and confirm it links to the original.
3. Issue a document in foreign currency, if you sell abroad.
4. Connect your store or clearing and confirm an automatic invoice is created per transaction.
5. Invite your accountant and see what they actually see.
6. Export a report - and check that data can leave, not only be viewed on screen.

The sixth item is forgotten and matters most over time. A system you cannot export data from is a system that will be expensive to leave.

What the system does not do

It is worth knowing what stays outside a focused system, so you do not discover it in month three:

• Payroll. An invoicing system is not a payroll system. A business with employees needs a separate solution.
• Complex inventory. Bills of materials, stock counts and warehouse locations are not part of what it presents.
• Project costing. Tracking budget against actual per project is a module with no counterpart here.
• Automatic bank statement import. Pulling bank statements is a capability that appears in systems aimed at accountants, not in every invoicing system.

If three of those four are relevant to you, you are no longer shopping for invoicing software but for a management system - a different decision entirely, discussed in migrating from Excel to an Israeli ERP.

Sources

• Morning by Green Invoice - company site
• Morning - plans and prices
• Morning - API documentation
• Israel Tax Authority - Israeli invoices, the official page
• Morning - the Israeli invoice model, the company's guide