Scribd
Upload
515 views6 pages

SW certificationProcedure-v1G

This document outlines the procedure for registering point of sale (POS) software in Ethiopia. It details that [1] POS software must be registered with the Ethiopian Revenues and Customs Authority if it is used to produce sales receipts. [2] The registration process involves submitting an application with documentation, signing a statement of compliance, and providing a software copy for testing. [3] The software will be inspected against standards by an appointed institution, and if approved, the Authority will register and publish the software's name and version.

Uploaded by

daniel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
515 views6 pages

SW certificationProcedure-v1G

This document outlines the procedure for registering point of sale (POS) software in Ethiopia. It details that [1] POS software must be registered with the Ethiopian Revenues and Customs Authority if it is used to produce sales receipts. [2] The registration process involves submitting an application with documentation, signing a statement of compliance, and providing a software copy for testing. [3] The software will be inspected against standards by an appointed institution, and if approved, the Authority will register and publish the software's name and version.

Uploaded by

daniel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Point of Sales Software Registration

Procedure

Ethiopian Revenues and Customs Authority

Draft by Goran Todorov and revised by Hailie Mekonnen, Dec. 2008.


1. Introduction
As per article 10 ‘Point of sale software requirements’ of Directive 46/2007 issued for the use
of Sales Register Machines, the Ethiopian Revenues and Customs Authority has prepared the
following procedure for registering software for the use of sales registers. This procedure
defines required characteristics of software applications to be used on Sales Register
Machines and the manner in which they will be used.

2. Basic Guidelines
1. POS software or a software package is required to be registered by the Ethiopian
Revenues and Customs Authority if it is to be used for control of trading goods and/or
services by producing a final receipt as output on a Sales Register Machine. It can be
produced and supplied by a company registered in Ethiopia or a company not
registered in Ethiopia.

2. For a company that produces the software locally application for registration shall be
accompanied by a Company Trade License, qualification form along with required
documentation, signed statement of compliance to standards and requirements which
shall be prepared by the tax authority as per the Directive 46/2007.

3. A Sales Register Software produced abroad is marketed locally for purposes of


producing sales receipts only if sold and supported by a local company or agent.

4. For a company that imports the software application for registration shall be
accompanied by the local Company’s Trade License, qualification form along with
required documentation, proof of software purchase from a company abroad, signed
statement of compliance to standards and requirements which shall be prepared by the
tax authority as per the Directive 46/2007.

5. The applicant/supplier is required to provide a compiled version of the software copy


along with a documentation that explains its use and all interfaces, what it is doing
and what it is not doing printed on CDs to the Authority for the test purpose.

6. Inspection of the software shall be conducted by appointed institution selected by


ERCA. All inspection shall be done and tests conducted based on the process flow
shown under section 3 of this document. All parameters to be checked during
inspection are attached as annex of this document. Representatives from applicant
and ERCA will attend the process while the inspector conducts its activities.

7. The inspector using a standardized format shall report to ERCA the final results in
two weeks time. Up on positive results, ERCA will register the software version as
officially certified and publish its name and version in a gazette and on the
Authority’s website.

8. The supplier is required to provide a copy of its software and documentation to the
Authority for archiving and future use in inspection activities.

Draft by Goran Todorov and revised by Hailie Mekonnen, Dec. 2008.


3. The Process Flow for Application and Software
Inspection

Applicant Submits Application


(accompanying documentation
and software sample as per
requirements in 2application
above)
Expert team receives
application

Application

No
Complete
?
Incomplete Application
Yes Software Copy along
with Documentation

Inspection is conducted Complete Application

Non Compliant Inspected


Software Software

Complete
No ?

Yes
Application and Software Copy
along with Documentation

ERCA Board receives


Application and
complete copy of
checked software
Registration Certificate

Draft by Goran Todorov and revised by Hailie Mekonnen, Dec. 2008.


ANNEX
Qualification Form

All data must be filled correctly.


1. SOFTWARE DATA
1. Type of Software Application
2. Name and version of Software
Model of Sales Register Machine
3. used with software (accredited
models only)

2. USER OR MANUFACTURER
WHO IS SUPPLYING THE DATA
SOFTWARE FOR REGISTRATION
1. Name and Surname
2. Company name
3. Position in company
4. Address
5. Mobile phone
6. Telephone
7. Fax
8. Email

3. SOFTWARE MANUFACTURER DATA


1. Full legal name
2. Address
3. City
4. Country
5. Telephone
6. Name of contact person for support
7. Web page and/or email

Draft by Goran Todorov and revised by Hailie Mekonnen, Dec. 2008.


For evaluation

Appendix
4. DOCUMENTATION Comment Grade
number
1. Commercial documentation of software application 1. +
User manual of software application with technical
2. data, instruction for installation, necessary hardware 2. +
requirement
Communication protocol (list of all commands which
are addressed to Sales Register Machine),
3. *in case that PC driver is used, the list of all 3. +
commands that driver gives to printer and the list of
commands that POS addresses to PC driver
4. Statement 4. +

5. REQUIRED FUNCTIONALITY Comment Grade


1. POS software must not allow printing of receipts to a
+
* printer other than a fiscal printer
2. A POS software application must be able to:
provide visual tracking of sales items, void and
a. +
refund function on the POS monitor
provide printing of each individual recorded sale on
b. +
fiscal receipt
provide printing of each individual recorded void on
c. +
fiscal receipt
provide printing of each individual recorded sale
d. +
refund on fiscal refund receipt
provide printing of each individual recorded void
e. +
refund on fiscal refund receipt
disable printing of non-fiscal documents which
f.
contain symbols that resemble the fiscal logo on non- +
*
fiscal printers, not fiscalized or fiscalized printers
disable further sales on POS in the absence of paper
g. +
or out of order status of the fiscal printer
h. provide printing of all items in POS database
provide printing of all non-taxable items in POS
i.
database
in case of electronic journal on fiscal device, must
securely store journal for user according to device
j. +
manual and use necessary tools for providing visual
presentation in case of auditing

Draft by Goran Todorov and revised by Hailie Mekonnen, Dec. 2008.


in case of electronic journal uploaded from fiscal
k.
device must secure back up of EJ files
provide printing of all fiscal reports on fiscal device.
l. For printing of Fiscal Reading Report, must provide
selection per date as well as per number of Z report.

*A software vendor is responsible for any wrong act due to POS errors or lax of security
while being developed and installed. In case if software vendor is operating outside Ethiopia,
the local agent/supplier of the software will be taking responsibility for any wrong doing due
to bugs or software coding not recommended in this guideline.

Draft by Goran Todorov and revised by Hailie Mekonnen, Dec. 2008.

You might also like