NZ743569A - Method and system for processing data that disagrees - Google Patents

Abstract

system for processing data sets that disagree, comprising: an input for receiving a plurality of data sets of corresponding elements from a respective plurality of corresponding users and to receive amendment input from at least one of the users; a memory for storing the plurality of data sets; a negotiation engine for comparing elements of corresponding elements of the data sets and identifying one or more corresponding elements of the data sets that are not in agreement across all of the data sets; an output for outputting the corresponding elements of the data sets that are not in agreement across all of the data sets to the users; and a prompts and messages engine configured to alert the users to the one or more elements of the respective data set corresponding to the respective user that are not in agreement across all of the data sets. The negotiation engine is further configured to respond to receiving amendment input by amending at least one of the data sets according to the amendment input and checking whether there remain any corresponding elements of the data sets that are not in agreement across all of the data sets. negotiation engine for comparing elements of corresponding elements of the data sets and identifying one or more corresponding elements of the data sets that are not in agreement across all of the data sets; an output for outputting the corresponding elements of the data sets that are not in agreement across all of the data sets to the users; and a prompts and messages engine configured to alert the users to the one or more elements of the respective data set corresponding to the respective user that are not in agreement across all of the data sets. The negotiation engine is further configured to respond to receiving amendment input by amending at least one of the data sets according to the amendment input and checking whether there remain any corresponding elements of the data sets that are not in agreement across all of the data sets.

Description

METHOD AND SYSTEM FOR PROCESSING DATA THAT DISAGREES Technical Field The present invention relates to a method and system for sing data that disagrees, and reconciling or resolving disagreement in such data sets.

Background Computing systems commonly se multiple data inputs, including in some cases from different sources and, in some instances, conflicts or istencies can arise between different data streams or data sets. Such inconsistencies are of particular n when two (or more) data streams or data sets are purportedly indicative ofa single physical or other parameter so should agree.

Such disagreement is handled in various ways. In some cases, two data streams or sets may ent a continuously variable natural parameter such that, while in ple the two data streams or sets should agree, a level of disagreement is tolerable. For example, the airtemperature indicated by the s of two closely situated digital thermometers should be identical, but small differences will commonly be encountered; in such a situation, reconciliation by averaging the two measurements will generally be acceptable.

In other cases, three or more data streams or sets that should agree may be received, but may be found not to agree. This eement may be resolved in a number of ways. For example, if one output disagrees with the other outputs, which are themselves in agreement, the divergent output is disregarded. Alternatively, if a first plurality of such outputs is in mutual agreement, and a second plurality of outputs is in mutual agreement and disagree with the first plurality, the second plurality of outputs may be disregarded. These ios can arise in, for example, during the automated control of vehicles employing multiple sensor inputs. rmore, data reconciliation may be required following relationship dissolution, such as in the division of property - during which different parties may have arrived at different estimates of respective assets and the like.

However, while some techniques for data reconciliation are known, even when such techniques are ed—and in scenarios where they are not employed— disagreement of data can impede the execution of subsequent processes. These subsequent processes may, for example, employ the data in which the disagreement has been detected, so it may not be le to proceed until the disagreement has been ed.

Summary of the Invention According to a first broad aspect of the present ion, there is ed a method for processing data sets that disagree, comprising: a) receiving a plurality of data sets of corresponding elements from a respective plurality of corresponding users; b) comparing elements of corresponding elements of the data sets; 0) fying one or more ponding elements ofthe data sets that are not in agreement across all of the data sets; d) outputting the corresponding elements ofthe data sets that are not in agreement across all of the data sets to the users er in the form of the names of those elements, their contents, or otherwise); e) alerting the users to the one or more elements ofthe respective data set corresponding to the respective userthat are not in agreement across all ofthe data sets (and optionally requesting amendment input); f) receiving amendment input from at least one of the users; 9) amending at least one of the data sets according to the amendment input; h) ng whetherthere remain any corresponding elements of the data sets that are not in agreement across all of the data sets.

In an embodiment, first and second data sets are received from first and second corresponding users. In this embodiment, the method comprises: a) receiving at least first and second data sets of corresponding elements from respective first and second users; b) comparing elements ofthe first data set and corresponding elements of the second data set; 0) identifying elements of the first data set that disagree with corresponding elements of the second data set; d) outputting the corresponding elements ofthe first and second data sets that disagree to the users; e) alerting the first userto the elements of the first data set that disagree with the corresponding elements ofthe second data set and prompting the second userto amend the ts of the second data set that disagree with the corresponding elements of the first data set; f) receiving amendment input from at least one of the first and second users; g) amending at least one of the first and second data sets according to the amendment input; and h) checking rthere remain any elements of the first data set that disagree with corresponding elements of the second data set.

It will be iated that, herein, whilst embodiments and scenarios may be described by reference to only two users/individuals and two corresponding data sets, this represents a minimum number of users and corresponding data sets.

The method may include repeating steps 0) to h) one or more times until there remain no corresponding elements ofthe data sets that are not in agreement across all of the data sets.

In an embodiment, the method includes at least lly further processing the corresponding elements of the data sets that agree across the data sets while continuing to resolve or ng resolution of disagreement between the one or more corresponding elements of the data sets that are not in agreement across all of the data sets.

In one embodiment, the method includes splitting each of one or more corresponding elements of the data sets into a ity of elements.

In one example, at least some ofthe elements of the data sets correspond to ial values. In one example, at least some ofthe elements of the data sets correspond to periods of time allocated to a given user.

In an embodiment, the method further comprises flagging the corresponding elements of the data sets that are not in agreement across all of the data sets (e.g. as “undecided” or “value to be agreed“), or storing orflagging the corresponding elements of the data sets that are not in agreement across all of the data sets as undecided.

In another embodiment the method further comprises displaying the elements or data indicative of the elements (e.g. the sum ofthe values ofthe elements or a map representation ofthe elements) to the users.

In an embodiment, at least some of the ts of the data sets correspond to assets, liabilities or financial resources ofthe users.

In another ment, at least some of the elements of the data sets correspond to child or other dependent access (such as child or pet access days).

When at least some ofthe ts ofthe data sets correspond to dependent access, the method may comprise presenting to a user a plurality of tools (constituting a data input mechanism) configured to control a child negotiation module that is controllable to negotiate the dependent access. The plurality of tools may comprise one or more of (i) a drop down menu listing common dependent access patterns, (ii) a grid sing one or more (‘n’) weeks (such as a fortnightly grid and/or as a n x 7 day grid), and (iii) a selectively viewable full calendar. These tools may be controllable to create access periods by creating and dragging and dropping blocks oftime.

The method may further comprise displaying the elements or data indicative of the elements (e.g. the sum ofthe values of the elements or a map representation of the ts) to the users grouped or flagged into a plurality of pools of elements. In this ment, the elements of the data sets may correspond to assets, liabilities or financial resources ofthe users and the pools of elements e pools corresponding to the respective assets, liabilities or financial resources of the respective users.

The pools of elements may include at least one pool of corresponding elements of the data sets that are not in agreement across all ofthe data sets. Furthermore, the method may include providing the users with a mechanism for moving at least some of the elements between pools.

In one embodiment, the method further comprises preparing tical information from two or more sets of the plurality of said sets of data, and sending respective messages based at least in part on the statistical information to one or more ofthe users. For e, the tive message may comprise at least one recommendation. The recommendation may end an expert (such as a psychologist or a valuer).

WO 17623 In an embodiment, the method further comprises generating either automatically or upon user prompting a data snapshot at a point in time comprising selected elements of the data sets and/or ofdata derived therefrom, and outputting the data snapshot, saving the data snapshot, or sending the data snapshot to one or more of the users.

In this embodiment, the data snapshot may comprise any one or more of (i) a financial statement, (ii) a financial negotiation outcome, and (iii) a dependent access outcome.

The method may e sending the data snapshot to one or more of the users for agreement.

The data snapshot may be loaded as the current state of any stage or stages of the method (such as into modules that ent the method), and may be used to contribute to an overall matter timeline which any of the users can rely on as a timeline for auditing or evidentiary purposes.

The method may also include measuring one or more financial ons at a point in time, such as for one or more commercial arrangements (e.g. family business succession when new partnering ements are being ished).

The method may include generating events that in aggregate comprise a matter timeline comprising one or more events ofthe method (whether the events are performed tically or in response to a user action).

According to a second broad aspect ofthe present invention, there is provided a system for processing data sets that ee, comprising: an input for receiving a plurality of data sets of corresponding elements from a respective ity of corresponding users and to receive amendment input from at least one ofthe users; a memory for storing the plurality of data sets; a negotiation engine for comparing elements of corresponding elements of the data sets and identifying one or more corresponding elements ofthe data sets that are not in agreement across all ofthe data sets; an output for outputting the corresponding elements ofthe data sets that are not in agreement across all ofthe data sets to the users; and a prompts and es engine for alerting the users to the one or more elements of the respective data set corresponding to the respective user that are not in agreement across all of the data sets (and optionally requesting amendment input); wherein the negotiation engine is further configured to respond to receiving amendment input by amending at least one ofthe data sets according to the amendment input and checking whetherthere remain any corresponding elements of the data sets that are not in agreement across all of the data sets.

In an embodiment, the method comprises a produce orders manager for producing orders indicative ofthe data sets d according to the amendment input.

Thus, the method may include producing orders indicative of the t state ofthe plurality of ts (such as contained in the various modules in the system implementing the ), and in response to relevant user input and consequential agreement between the users.

In an embodiment, the system is configured to: i) identify one or more corresponding ts of the data sets that are not in agreement across all of the data sets; ii) output the corresponding elements ofthe data sets that are not in agreement across all of the data sets to the users; iii) alert the users to the one or more elements ofthe respective data set corresponding to the respective userthat are not in agreement across all ofthe data sets; iv) receive amendment input from at least one of the users; v) amend at least one of the data sets ing to the amendment input; and vi) check whetherthere remain any corresponding elements of the data sets that are not in agreement across all of the data sets.

The system may be configured to repeat steps i) to vi) one or more times until there remain no ponding elements of the data sets that are not in agreement across all of the data sets.

The system may be configured to at least partially further process the corresponding ts of the data sets that agree across the data sets before disagreement between the one or more corresponding elements ofthe data sets is resolved.

In an embodiment, the system is controllable to split each of one or more corresponding elements of the data sets into a plurality of elements.

In an embodiment, at least some of the ts of the data sets correspond to: i) financial values; ii) assets, liabilities orfinancial resources ofthe users; and/or iii) dependent access (such as child or pet access days).

When at least some ofthe elements ofthe data sets correspond to dependent access, the system may include a child negotiation module controllable to negotiate the dependent access and having a plurality oftools (constituting a data input mechanism) presentable to the user, wherein the tools are configured to control the child negotiation module. It will be appreciated that, though referred to as a child negotiation module, this module may alternatively be referred to as a dependent negotiation module as the onality for negotiating access to children, pets and other dependents is identical.

The plurality oftools may comprise one or more of (i) a drop down menu g common dependent access patterns, (ii) a grid comprising one or more (‘n’) weeks (such as a fortnightly grid and/or as a n X 7 day grid), and (iii) a selectively viewable full ar. These tools may be controllable to create access periods by ng and dragging and dropping blocks of time.

In one embodiment, the system is operable to flag the ponding elements ofthe data sets that are not in agreement across all ofthe data sets, or store or flag the corresponding ts of the data sets that are not in agreement across all of the data sets as undecided.

The system may be configured to display the elements or data tive of the elements to the users.

The system may be configured to display the elements or data indicative ofthe elements to the users grouped or flagged into a plurality of pools of elements. 2016/051292 The system (for example in a financial statement module) may be configured to display the elements or data indicative ofthe ts to the users in column format (to cater for a plurality of users, with one column per user).

The system (for example in a financial statement module) may be configured by the user to display the elements or data indicative of the elements to the users as lists where there are two users, with each user being able to select a preferred view separately (column or list). Thus, a list format allows easier rendering on smaller device screens, such as on mobile phones or tablets or laptops with smaller screens or screen capacity.

In an embodiment, the ts ofthe data sets correspond to assets, liabilities or financial resources ofthe users and the pools of elements include pools corresponding to the respective assets, ities or financial resources of the tive users. In this embodiment, the pools of elements may include at least one pool of corresponding elements of the data sets that are not in agreement across all of the data sets. The system may include a reallocation mechanism operable to move at least some of the elements between pools.

In an embodiment, the system further comprising a monitoring and reporting engine.

The monitoring and reporting engine may be configured to prepare statistical information from two or more sets ofthe ity of said sets ofdata, wherein the s and messages engine is further configured to send respective messages based at least in part on the statistical ation to one or more ofthe users. For example, the respective message may comprise at least one recommendation. The recommendation may recommend an expert (such as a psychologist or a ).

The system or its component s (e.g. a financial statement, a financial negotiation, a child negotiation or a produce orders module) may be configured to generate either tically or upon user prompting a data snapshot at a point in time comprising selected elements of the data sets and/or ofdata derived therefrom, and to output the data snapshot, save the data snapshot, or send the data snapshot to one or more of the users.

WO 17623 The system or one or more of its component modules may be configured to generate events that in aggregate comprise a matter ne comprising one or more events in the system.

According to a third broad aspect of the present invention, there is provided computer software configured to, when executed by one or more processors of a ing device, l the device to ent the method ofthe first broad .

According to this aspect, there is also provided a computer readable medium comprising such computer software (in one example stored in non-transitory form).

It should be noted that any of the various individual features of each of the above aspects of the invention, and any ofthe various individual features of the embodiments described herein including in the claims, can be combined as suitable and desired.

Brief Description of the Drawings In order that the invention can be more clearly ascertained, embodiments will now be described, by way of example, with nce to the anying drawings, in which: Figure 1 is a schematic diagram ofa system for performing data reconciliation according to an embodiment of the present invention; Figure 2 is a schematic view ofthe page displayed by the login module ofthe system of figure 1 according to an embodiment of the present invention; Figure 3 is a schematic view ofthe ed fields displayed by the login module of figure 2 according to an embodiment of the present invention; Figure 4 is a schematic view of a profile page generated by the profile module of the system of figure 1 according to an embodiment of the present invention; Figure 5 is a tic view ofthe page displayed by the financial statement module of the system of figure 1 according to an embodiment ofthe present invention; Figure 6 is an example ofASSETS or LIABILITIES displayed by the financial ent module of figure 5 according to an embodiment ofthe present invention; Figure 7 is a schematic view 140 ofthe page generated by a financial negotiation module of the system of figure 1 according to an embodiment ofthe present ion; Figures 8A and 88 present a schematic view of the page generated by the child negotiation module of the system of figure 1 according to an embodiment ofthe present invention; -10— Figure 8C is a schematic view of the page generated by the child negotiation module of the system of figure 1 according to another embodiment of the present invention; Figure 9 is a schematic view ofthe page generated by produce orders manager of the system of figure 1 ing to an embodiment of the present invention; Figures 10A and 1GB present a flow chart ofthe s implemented by the financial statement module of the system of figure 1 according to an embodiment of the present invention; Figures 11A and 11B present a flow chart ofthe process implemented by the financial negotiation module of the system of figure 1 according to an embodiment of the present invention; and Figures 12A and 128 present a flow chart ofthe process implemented by the child negotiation module ofthe system of figure 1 according to an embodiment of the present invention.

Detailed Description According to an embodiment of the present invention, there is provided a system 30, as shown in high-level architectural form in figure 1, for ming data reconciliation according to an embodiment of the present invention. System 10 facilitates the reconciliation of plural parallel data streams or data sets that contain data eements. ln broad terms, system 10 is adapted to receive these data streams or sets from a plurality of users. In the example presented below, the data concerns personal, relationship, related and ial details for use during mediation, negotiation and settlement. This allows the users to employ system 10 to negotiate financial and child- or pet-related outcomes from, for example, home. System 10 es consent order tes, and is configured to generate consent orders based on the data streams or sets once iled and agreed by the users, for ement—for example—by a Court or other appropriate authority, such as by interfacing with the Court’s case management system.

System 10 is also adapted to provide referrals to s (e.g. asset valuers, child psychologists) as desired, and is configured to protect private ation and is operable to purge selected (e.g. financial) information relating to a specific matter once the relevant phase has been completed. System 10 allows parties related to the users (e.g. family members) to participate in the settlement process, and for associated _11_ parties (such as legal representatives) to observe the process without participating directly in the negotiation.

For convenience, the service implemented by system 10 is referred to herein as ‘My tion’ or ‘SimplySeparate.com’.

System 10, by facilitating the division of financial resources and the resolution of child and/or pet access, may reduce demand for Court time (judges, associates, and facilities) and expense, as well as personal time, expense and acrimony. System 10 can be used in the separation of assets and the agreement on child access at any point in a relationship but will typically be employed during the break-down of the relationship. System 10 can also be used to capture relationship and financial information at the commencement of co-habitation, support relevant mediation during a relationship, and t on-going negotiation, such as of child access, after final settlement and orders are obtained from the Court. For example, the tool to support agreement of child and/or pet access can be used each school term or each year to agree on child or pet access forthe following period, allowing adjustments to be made as children or pets grow up. The same tools can also be used to e one or more financial ons at a point in time for a range of commercial ements including family business succession when new partnering arrangements are being established.

The key functions of system 10 include: 1. Capturing information about the individuals that is required to agree on an outcome (including reconciling ences in inputted data) and to nt that outcome (pertaining to, for example, financial s and children); 2. Documenting the financial position (including agreeing on values of assets, liabilities and financial resources); 3. Negotiating a financial split which can be done in the couples own time, and from the comfort oftheir own homes (compared to today where lawyers and a mediation facility are , and the solicitors and barristers charge for the time that the couple are actually considering their outcomes); 4. Negotiating child and/or pet access to y for all interested parties and minimise ent to the children; . Producing a set of Consent Orders for review and sation by lawyers and/or a Court. -12— System 10 includes workflows that encourage consensus and prompt ss, to ameliorate the emotional stress associated with relationship dissolution. System 10 is adapted to accommodate a range of relationship types, financial lio xity, and child parenting or pet care arrangements, and will support multiple jurisdictions.

System 10 comprises several layers: a user interface/front end 12, a middleware layer 14, an application layer 16, a database/back-end 18, a network/communications layer , and a hardware/physical layer 22.

User interface/front end 12 includes a p browser web page 24 and a mobile browser web page 26, built using known web technology, such as HTML5, CSSB and/or Flash 28; the primary mechanism to access system 10 is thus via a web browser. User interface/front end 12 also includes a mobile application 28: a subset of features may be provided to native applications built for mobile devices using the iOS and Android ecosystems.

Security Management System 10 may be hosted with an external provider with an Application Service Architecture (ASA) ch providing infrastructure as a service. The service provider may have a database-generated encryption key for communications to and from the web server, and optionally a Hardware Security Module (HSM). The database server using the hardware device automatically and transparently encrypts stored data. The Application layer will also be responsible for encrypting ed data as part ofthe defined business logic. The user will have minimal or no responsibility for tion, and the majority ofthe encryption will occur underthe l of the Synchronisation Manager (described below) of application 16.

System 10 implements ased access to application functionality and record-level access to the underlying database, sing at least four roles with the following access matrix: -13— cial F_inancial C_hild Produce P_rofile WW__ StatementNeotiationl\le:otiatim1 Orders IRVVX RVVX nulli—Party/Guest Configure Monitor AdmInIstrator- - aMal‘iIcZEJiSnpp health Manage accounts Database Maintain Administrator Middleware layer 14 of system 10 includes a security management tool 32 including ated processes to add, delete or modify the access rights and permissions for roles and individual users. This may be provided by the hosting and application service provider, but can be — as described above — an in-house function.

Security management tool 32 may make use of a database to user, account and role based access sion data. Middleware 14 also includes a transaction manager 34, a process trator 35, an interface gateway 36 and an audit engine 37.

Transaction manager 34 is a Transaction Management Layer, provided to support n-based access to system components and services provided by application 16 and back-end 18. Process orchestrator 35 may be implemented, to provide process orchestration, either within transaction manager 34 or - as illustrated — as a separate component within middleware layer 14.

Application 16 has core components 38 for ng profiles, financial statements, financial negotiation, child ation and orders (described below). Application 16 includes a profile module 40, a business rules engine 41, a ring and ing engine 42, a synchronization manager 44, a produce orders manager 45, a submit orders manager 46, a financial statement module 47, a negotiation engine 48 (which includes a financial negotiation module 49 and a child negotiation module 50), a prompts and messages engine 52, a rendering engine 54, a billing engine 56, and a referrals engine 58. Core components 38—although ed as a discrete set of elements in figure 1—are implemented by—im‘er alia—profile module 40, business rules engine 41, monitoring and reporting engine 42, synchronization manager 44, 2016/051292 _14_ e orders manager 45, submit orders manager 46, financial statement module 47, negotiation engine 48, s and messages engine 52, rendering engine 54, billing engine 56, and als engine 58. It should be noted that, though referred to as a ‘child negotiation module’, child negotiation module 50 can be used to negotiate access, etc, in respect of other dependents, such as pets.

Database/back-end 18 includes a matter database 60, a database management system 62, a ty/account/user database 64, an order templates and rules database 66 and a referrals database 68.

Network/communications layer 20 implements TCP/IP 72. Hardware/physical layer 22 includes a clustered / cloud application server 74, a clustered / cloud database server 76 and a clustered / cloud middleware server 78.

Security management tool 32 manages tion of relevant user-related data, and may interact with business rules engine 41 of application 16, database management system 62 of database/back-end 18, transaction manager 34 and process orchestrator of middleware layer 14, and the various components ofapplication 16 so that personal and private data are handled securely and appropriately in an integrated fashion.

Transaction Management, Process Orchestration and Component Integration System 10—via middleware layer 14 and/or application 16—provides web services (e.g. REST or SOAP) based APls invoked by user ace/front-end 12. The actual approach may be constrained by what is available via the application service provider.

Core Application Components As described above, the core functionality 38 of ation 16 comprises a number of s, one for each user-facing component, including: 1. Login /Account Setup Profile ial Statement Financial Negotiation Child Negotiation 97.01999!” Orders 2016/051292 -15— Negotiation Engine Negotiation engine 48 facilitates reconciliation of a plurality of distinct data streams or sets, such as data submitted by two or more parties or individuals using system 10.

This allows a plurality of s or individuals to reconcile such data by, in effect, negotiation. For e, this mechanism can be used to negotiate financial and child access outcomes. In the example of a relationship break-down, there are typically two y individuals ed, but in other examples there may be more than two individuals engaging in such a negotiation.

Negotiation engine 48 supports the participation of at least two individuals during the negotiation s, so negotiation engine 48 can be used more broadly than simply to negotiate financial matters and child access. It may also be used to facilitate estate division (viz. will-related negotiations) and in business matters such as succession planning.

The logic in the core application components 38, the t state of the negotiation (as stored in matter database 60 and other system databases), input from the users (via a user input/output, not shown), input from business rules engine 41, input from synchronisation manager 44 and input from other system components (such as transaction manager 34 and process orchestrator 35) are used by application 16 to update the current state ofthe negotiation.

Negotiation engine 48 supports both turn- based, and parallel negotiation approaches, e auction, and conventional bidding approaches.

Business Rules Engine Business rules engine 41 encodes ss rules relevant to particular modules or components. For example, a business rule may state that: IF a user wants to make use of the Child Negotiation functionality, then the Child Names, Ages and Birthdays need to be populated in the e Page.

Prompts and Messages Engine Application 16 is configured to encourage consensus and to accelerate resolution. To that end, application 16 ys on-screen messages or sends reminders (e.g. time based) to the users as they progress through a negotiation. (A display is not depicted in figure 1, but it will be appreciated by those skilled in the art that such displaying— -16— here and as discussed elsewhere herein—will typically be done to the display of the respective users’ personal computing device (whether desktop computer, mobile device or otherwise). These messages are rules based. Prompts and messages engine 52 may be a separate nd component of application 16 (as illustrated) or be ented as part of business rules engine 41.

Examples of rule-based messages that may be displayed on certain pages of the website include: 1) RULE: When the % (by value) of assets agreed between the negotiating parties exceeds 80%, display a message “You’re almost there, only $x (y items) to agree and you’re done. Keep going!” 2) If negotiation has been underway (from the time ofthe first sync) for more than two months and the users have not logged in, email individuals a message: “We t seen you for a while. Congratulations if you have managed to reach agreement. If not, we are here to help you. Just click here: [insert linkto website]” (final messages and rules to be confirmed) Prompts and messages engine 52 inserts messages, once displayed, into a back-end message log (not shown) to facilitate the optimization of the ncy and repetitiveness of messages. For e, prompts and messages engine 52 will refrain from annoying a user by sending the same “you have achieved 80% agreement” multiple times in a short period of time.

Monitoring and Reporting Engine Monitoring and reporting engine 42 summarises statistics h no data about individual matters or individuals is accessible) ning numbers of matters, matter duration, demographics of the users, average ial portfolio value. Monitoring and reporting engine 42 can be controlled to present these statistics graphically and allow filtering by any ofthe dimensions in the underlying se, such as time period, postcode and other demographics, lio value and so forth.

The reporting and monitoring analytics generated by monitoring and reporting engine 42 may be provided to s and messages engine 52 as input into es to be presented to users. For example, a message may be presented indicating that the financial or child time split is within x% of the mean of the past y settlements facilitated by application 16. -17— Synchronisation Manager Synchronisation manager 44 manages synchronisation of sessions between users.

Synchronisation manager 44 makes use of other system components (such as business rules engine 41) or may n the synchronisation ols (including encryption).

Rendering Engine ing Engine 54 takes raw information that is stored in the various databases 60, 64, 66, 68 of system 10 (eg. the current state of negotiation from each individual’s perspective), and renders the data in manner subject to presentation tes of system 10 (not shown) that define the ‘look and feel‘ of each system component.

Rendering engine 54 takes input (the current state) from negotiation engine 48 and manages the rendering of the resultant screens in the user interface/front-end 12.

Rendering engine 54 also contains rendering rules that take into consideration the nature ofthe user device (eg. PC, mobile phone, table or watch) and adjusts the rendering to match the display capabilities of the target user device.

Produce Orders Manager Produce orders manager 45 manages the production of draft orders. Produce orders manager 45 may draw input from the components of application 16, may employ their associated data, and may receive input from business rules engine 41 or other system s, as well as ct with transaction manager 34 and process orchestrator 35.

Orders need to be compliant with the relevantjurisdiction where they are to be submitted (for endorsement by the relevant Court or authority), so order templates and rules database 66 includes geographically- sdictionalIy-localised orders templates and order production rules.

Submit Orders Manager Submit orders r 46 interfaces with the relevant Family Court ry systems.

The registry systems will be specific to the relevant Court and jurisdiction, so submit orders manager 46 is configured to interface with a range of such external systems via interface y 36 of ware 14, which provides web services to push data to target external systems, and or use pull web services from the external registry systems to carry out the submissions. Submit orders manager 46 may make use of WO 17623 -18— business rules engine 41, transaction manager 34, process trator 35 and synchronisation manager 44, and other system engines or components.

Interface Gateway Interface gateway 36 facilitates all in-bound and out-bound data transfers to and from system 10. Interface gateway 36 is used by submit orders manager 46 to interface with Court registry systems, but may also be used to interface to othertypes of third- party systems such as database and booking s for financial and psychiatric or psychological experts. There are a number of components of system 10 that can trigger referrals to such s for specialist advice such as asset valuations and family s, and such requests or bookings or referrals can be facilitated by interface gateway 36.

Audit Engine Audit engine 37 monitors progress, and logs and time-stamps each ction all individuals have with application 16. These interactions include but are not limited to: the date and time that each individual first registered with the website, when they purchased each paid module (if they did), the date and time the individuals commenced ating their financial and/or child access settlement, the date the individuals reached agreement on inancial and/or child access settlement, the date and time of the t set of consent orders and so forth. Audit engine 37 manages an audit log ortable (not shown), stored in matter database 60, which allows monitoring and reporting engine 42 also to track average time to reach agreement across the various matters facilitated by system 10.

For each message communicated to a user, an entry is made in the audit table / matter feed with a date (ddzmmzyyyy) and timestamp (hh:mm:ss). For each item added to the Audit Table / Matter Feed, the nt Matter ID and Participant ID forthe initiator is added to the audit table. Items in square brackets in the following table of Business Requirements of Audit Entries (stored in and managed by business rules engine 41) are field names to be populated. _ 19 _ Source Tri99er Messa9e Module New Userjoined - new Participant A user si9ns u p ID Particioant ID created created New Matter Commenced - new A new Matter d Matter ID Matter ID created A Participant invites another Participant cipant ID] invited Participant [Invitee Name] A PartICIpant JOIns a Matter by. . . . Participant [Participant ID - Invitee] Jo'ned Matter-[Matteir ID]Ft:y. . accepting an invitation from . . another Participant accepting an InVIte Irom artICIpant _ [PartICIpant ID - anIter] LogIn Participant cipant ID - Invitee] A Participant joins a Matter by joined Matter [Matter ID] entering a entering a Matter ID Matter ID A participant invites another Participant [Participant ID] d user to be a "view only" user VIEW ONLY user [Invitee Name] Participant cipant ID - Invitee] A Participant joins a Matter as a joined Matter [Matter ID] as a "view "view only“ user by accepting an only" user by accepting an invite invitation from r from Participant [Participant ID - Participant Inviter] Profile saved Participant [Participant ID] saved their profile Profile PartICIpant [PartICIpant ID]. . . .

Profile complete completed their profile F!r$t use Of (Cl'Ck on) the. . Participant [Participant ID] accessed the Financial ent FinanCIal Statement Module for the first time When a Participant initiates a Ipant CIpant ID] synced. . . . sync of their Financial their FinanCIal Statement —disputedAn ASSET valueis Asset [Asset ID] is disputed d—sputedA LIABILITY valueis Liability [Liability ID] is disputed A FINANCIAL RESOURCE Financial Resource [Resource ID] value is disputed is disputed Financial An ASSET value is agreed Asset [Asset ID] is agreed Statement A LIABILITY value is agreed Liability lity ID] is agreed A FINANCIAL RESOURCE Financial Resource [Resource ID] value is agreed is agreed New ASSET added by Participant New ASSET added [Participant ID] - new Asset ID ([Asset ID]) created New LIABILITY added by New LIABILITY added Participant [Participant ID] - new Liability lD ([Liability ID]) created WO 17623 -20— New FINANCIAL RESOURCE Financial Resource [Resource ID] added is added Asset [Asset ID] deleted by An ASSET is deleted Participant [Participant ID] A L'AB'L'TY '5 de'eted.

Liability [Liability ID] deleted by Particioant Particioant ID A FINANCIAL CE is ial Resource [Resource ID] deleted is deleted Participant [Participant ID] First use of (click on) the accessed the Financial Negotiation Financial Negotiation Module Module for the first time When there are 2 2 users with access to the Financial Negotiation Module, and one Of Financial Negotiation commenced them drags an item from the on Matter [Matter ID] undecided list for the first time (i.e. the time the negotiation started A ipant clicks on an offer Participant [Participant ID] clicked for a 3rd-party recommendation on Link {Referral Link ID] Participant [Participant ID - offerer] A Participant sends an offer to sent an offerto Participant another ipant [Participant ID - offeree] Participant [Participant ID - offeree A Participant accepts an offerto accepted an offer from Participant another Participant Financial Particiant ID - offerer Negotiation When a Participant initiates a Participant [Participant ID] synced sync of the Financial Negotiation their Financial Negotiation Module Module 2 50% of the Net Assets agreed 2 50% of the Net Assets agreed 2 80% ofthe Net Assets agreed 2 80% of the Net Assets agreed 100% or more of the Net Assets 100% or more ofthe Net Assets agreed agreed An ASSET has been split Asset [Asset ID] has been split between two or more between Participants [List of Participants Participant IDs] A LIABILITY has been split Liability [Liability ID] has been split between two or more between Participants [List of ipants Participant IDs] A FINANCIAL RESOURCE has ce [Resource ID] has been been split between two or more split between Participants [List of ioants ioant IDs Elgsgtoltjizetzigr: filgcékufen) the Chlld. . . ipant [Participant ID] accessed the Child Negotiation Child Ne9otiation Module fort-he. first time When there are 2 2 users With. Child Negotiation commenced on access to the Child Neootiation Matter [Matter ID] W0 2017l117623 -21— Module, and one of them picks one or more days on the calendar for the first time or uses one of the drop down patterns (i.e. the time the negotiation started) A Participant clicks on an offer Participant [Participant ID] clicked for a 3rd-party recommendation on Link {Referral Link ID] npant [Pamc'p‘i‘Ut ID ' offerer] A Participant sends an offer to sent an offerto PartICIpant another Participant Partici ant ID - offeree A Participant accepts an offerto npajnt [Pafgmfam :3 ' offereean 0 er rom arttcnpant r Participant accepte [PartICIpant ID - offerer] When a Participant tes a . . . .

. . . . Partncnpant [PartICIpant ID] synced sync of the Fmancral Negotiation their Child Negotiation Module Module 2 50% oftime has been agreed 2 50% of time for Child [Child ID] for a Child agreed 2 80% of time has been agreed 2 80% of time for Child [Child ID] for a Child agreed 100% or more of time has been 100% or more oftime for Child agreed fora Child [Child ID] agreed When a user clicks on the Participant [Participant ID] viewed Orders Module (prior to the Orders Module .urchase The first time any of the users Participant [Participant ID] used the starts using the Orders Module Orders Module for the first time (e.g. g in questions) The first time all the relevant information to produce a set of Ready to produce orders forthe complete orders is captured in first time the s stem Each time a user with access to Orders the Orders Module presses the Participant cipant ID] initiated Orders button to generate draft order production orders Draft set of child interim orders has has been oenerated been oenerated Draft set of financial interim orders orders has been ted has been generated Draft set of child final orders has has been generated been generated Draft set of financial final orders orders has been generated has been generated Participant [Participant ID] When a user purchases the . . purchased the Financial Fmancnal Negotiation Module. . g Negotiation Module When a user purchases the Participant [Participant ID] Child Negotiation Module purchased the Child Negotiation 2016/051292 -22— Module Participant [Participant ID] Orders Module sed the Orders Module ipant [Participant ID] monthl commenced monthl subscriotion . susperri)ded [their mronthlyPartici ant Partici ant ID] monthly subscription subscription. .

Participant [Participant ID] re- y subscription instated their monthly subscription New Expert joined - new Expert ID A new expert signs up Expert ID created]) created Expert Expert tes Profile Directory Eggs: [Expert ID] completed the" Expert selected by PartICIpant. . Expert t ID] profile selected by Participant [Participant ID] Billing Engine Billing engine 56 manages g and payment for activation ofthe paid modules or components ofthe system, such as financial negotiation and child negotiation modules 49, 50 of negotiation engine 48 and produce orders manager 45.

Billing engine 56 may also use interface y 36 to coordinate payments with third- parties such as financial services organisations, credit card providers and other ial clearing houses.

Referrals Engine There are various stages in the financial and child negotiations where experts are needed to provide input or to break a deadlock. Referrals engine 58 manages the storage of information regarding experts (e.g. child psychologists, property s or others). The information stored regarding each expert includes an expert e, submitted by the respective expert (using an expert profile module (not shown), which requests more information than is requested by profile module 40) upon that expert registering with and signing into system 30. Financial negotiation and child negotiation modules 49, 50 of negotiation engine 48 may display links to the relevant lists of experts, which are drawn from referrals database 68 and facilitated by referrals engine Optionally, referrals engine 58 may also draw information from other system databases, such as the status of a given financial or dependent (child, pet, etc) -23— negotiation from matter database 60, to determine the context and the appropriate referrals to offer a user.

System 10 also allows experts to be registered (by themselves and / or by the site operators) and allows records about a given expert to be , ed, hidden, copied and deleted.

Figure 2 is a schematic view 90 of the page yed by the login module of application 16. The login module allows users to sign-up to use the onality of the site provided by web pages 24, 26, as well as log-in to the secure parts of the site if previously registered. Use of this module is free.

Figure 3 is a schematic view of a pop-up screen 100 with the required fields, as displayed by the login module in a table, grouped as s: 0 User ID (enter email address) 0 rd (enter password) 0 Register button for new users The business rules implemented by the login module, and associated with the unique matter identifier (Matter ID) are as follows: 0 Matter ID (greyed out, a 10 digit incrementing number e.g. 0000000001 0 IF Individual 2 is invited to participate or a third-party is invited to SHARE (refer Profile page), THEN the Matter ID is embedded in that link and is automatically assigned] 0 IF a Matter ID exists, during the new sign-up process (i.e. the other individual has y signed-up and a Matter ID created), THEN there is a field to enter the Matter ID which links the second individual to the matter 0 IF the sign-up is a result of an invitation from the other individual, THEN the Matter ID will already be populated and greyed out c There is a way to add a Matter ID even after the account has been created in case it has not yet been ed at the time of creation of the second individual’s account If login is unsuccessful, then a retry is afforded with a maximum of 3 attempts and, if still unsuccessful, an email is sent to the user regarding the 3 failed attempts. If successful, system 10 presents pop-up screen 100 (see figure 3) and the option to select return to <Iast screen> or first screen based on the progress ofthe last session.

If the use of the modules ‘Financial Negotiation’ OR ‘Child Negotiation’ OR ‘Produce Orders’ (implemented by negotiation engine 48 and produce orders manager 45) is not purchased, then pop-up screen 100 does not include the relevant Page names, and the relevant labels indicating those modules are greyed out and cannot be clicked on in the session.

A set of breadcrumbs is displayed on the top of each module / page. Initially, the breadcrumb labels are: 1. Profile 2. Financial ent 3. Financial Negotiation 4. Child Negotiation . Produce Orders lly, the Financial Negotiation, Child Negotiation and Produce Orders breadcrumbs are visible but greyed out. IF the user clicks on a greyed-out breadcrumb, they MUST be taken to the nt page which is yed greyed out. The user is prompted to purchase the module to make use of it. Billing engine 56 facilitates the process of users purchasing the paid modules in the website.

Profile Figure 4 is a schematic view of a profile page 110 generated by profile module 40 of application 16. Profile module 40 allows a userto capture personal information about themselves and their relationship partner, information about the relationship, and also information about any children and/or pets. This ation is used by system 10 to allow the use of other optional es of the site such as the child negotiation functionality, as well as to populate the relevant parts of the draft consent orders if the individual chooses to use that functionality. However, profile module 40 is not controllable to edit personal information (e.g. name) about any other participant in a given matter . Use of this module is free.

Business Requirements / Rules The profile page 110 is common to both users so either individual can use this module to edit information in this page. This page includes the following fields, displayed in a table, d as follows: W0 2017l117623 -25— If the other dual has commenced use of ‘My tion’, then profile module 40 uses the same Matter ID.

RELATIONSHIP O Name of Individual 1 (mandatory) O DOB of Individual 1 (optional — used for Child ation and Produce Orders) Name of Individual 2 tory) DOB of Individual 2 (optional — used for Child Negotiation and Produce Date of cohabitation (mandatory) Date of marriage (optional) Relationship participant flag for Individual 1 — HUSBAND, WIFE, PARTNER (mandatory) Relationship participant flag for Individual 2 — HUSBAND, WIFE, PARTNER (mandatory) Relationship type to dependent 1 for Individual 1 — FATHER, , AUNT, GRANDPARENT etc O Relationship type to dependent 2 for Individual 1 — FATHER, MOTHER, AUNT, GRANDPARENT etc O Relationship type to dependent 1 for Individual 2 — FATHER, MOTHER, AUNT, GRANDPARENT etc 0 Relationship type to dependent 2 for Individual 2 — FATHER, MOTHER, AUNT, GRANDPARENT etc CHILDREN Do you have children? Y/N If Y, then: Child name 1 (optional) Gender (optional but mandatory if name populated) DOB Child 1 nal but mandatory if name populated) Child name 2 (optional) Gender (optional but mandatory if name populated) DOB Child 2 (optional but mandatory if name populated) There is a + and — button positioned t “Child name n” (where n is the last child in the list, in this example 2) to add more children (which will add their name, gender and DOB). There are fields for two children when profile page 110 is initially displayed. If a WO 17623 -26— child is to be deleted, then a confirmation pop-up “Confirm you want to delete Y/N” is displayed.

PETS 0 Do you have pets? Y/N if Y, then: 0 Pet name 1 (optional) 0 Pet name 2 (optional) A + and — button is positioned against “Pet name n” to add more pets (where n is the last child in the list). There are fields fortwo pets when the screen is initially displayed.

If a pet is to be deleted, then a confirmation pop-up “Confirm you want to delete Y/N" is displayed.

Where Individual 1 wants to invite dual 2 to the negotiation, a pop-up screen is displayed to Individual 1,which allows input of an email s to send an invitation to Individual 2. The Matter ID is embedded into the invitation and automatically populated for the invited party.

Where one individual wants to share with a trusted friend, a pop-up screen is displayed that allows input of an email address to send an invitation to a third-party. The third- party needs to er with the website and is prompted to do so once they click on the link from the email that they receive. There is no login screen for a trusted friend and the read only n is t for only a point in time for when the link is clicked on (not updated dynamically).

Financial Statement Figure 5 is a schematic view of a financial statement page 120 displayed by financial ent module 47 of application 16. Financial statement module 47 allows an individual of the plurality of users to input their portfolio of assets, liabilities and financial resources, which is a key input into any subsequent financial negotiation, and into the draft consent orders if the user chooses to use this functionality. In the case of two individuals using this functionality to capture theirjoint financial position, the site will flag where individuals do and do not agree on the value of a given asset, liability or financial resource. Use ofthis functionality is free. -27— Business Requirements / Rules The most common ASSETS and LIABILITIES are displayed in a table with an input for the corresponding value r amount) and any associated ity (dollar amount) The grid includes a comment field to allow entry oftext notes to uniquely identify the financial statement item (e.g. the street address of a property).

The most common Asset classes include: 0 Primary Residence 0 Investment ty 1 0 Car 1 0 Furniture 1 0 Art work 1 o nnuation Individual 1 o Superannuation Individual 2 0 Personal items 1 o Etc.

The most common LIABILITY classes e: 0 Mortgage 0 Personal Loan 0 Overdraft 0 Credit Card 0 Car Loan / HP / Lease There is a + and — button to add and delete additional ASSETS, LIABILITIES or FINANCIAL RESOURCES; selecting these buttons respectively adds rows to and deletes rows from the table. Any ASSET, LIABILITY or FINANCIAL RESOURCE whose value is not agreed at the commencement or during financial negotiation is listed in a “VALUE TO BE AGREED” pool in the financial negotiation page 120. If the ASSET, LIABILITY or FINANCIAL RESOURCE value is not agreed on, the values that each individual has d are displayed against the relevant ASSET, LIABILITY or FINANCIAL CE on the financial negotiation page. Referring to figure 6, for example, the label against the relevant ASSET, LIABILITY or FINANCIAL RESOURCE is “Individual 1 Name: $value” in a first box 132, and “Individual 2 Name: ” in a second box 134 below the first box 132, with a red line (shown as dashed line 136) surrounding both boxes 132, 134. -28— If the ASSET, LIABILITY or FINANCIAL RESOURCE value is not agreed on, then the values that each individual has entered are displayed t the relevant ASSET, LIABILITY or FINANCIAL RESOURCE in the “VALUE TO BE AGREED” pool on the financial negotiation page. Again, the label against the relevant ASSET, LIABILITY or FINANCIAL RESOURCE will be “Individual 1 Name: $va|ue“ in a first box, and “Individual 2 Name: $va|ue” in a second box below the first box, with a red line surrounding both boxes.

An individual can agree to the other user’s valuation by selecting the value box provided by the other individual and ng it onto their corresponding value box in financial statement page 120 or by messaging a revised estimate to the other Individual for agreement. Alternatively, the individuals can click on their value box (local ir session) forthe given ASSET, LIABILITY or FINANCIAL RESOURCE, and enter the same value into their respective Financial Statements for the given ASSET, LIABILITY or FINANCIAL RESOURCE. Once the value is agreed on by the parties, the two value boxes will se into a single box, the red line surrounding the boxes is removed, and the two values for the relevant ASSET, LIABILITY or FINANCIAL RESOURCE are ed into a single value in the Financial Statement page on the individual’s local session and synced with the other individuals valuations once the “sync Financial Statements” link or button (at 122 of figure 5) is selected. It should be noted that, fora given individual, the test of whether a value is d’ is whether it agrees with the corresponding value ed by the other individual—or individuals—as at the last time the financial statements were synced. If, however, the other (or r) individual has changed the value ofthe ASSET, ITY or FINANCIAL RESOURCE since the last sync, it may arise that one individual may think he or she is agreeing to the other (or another) individual’s value only to have it remain not agreed once the financials are synced again.

Once the value of a disputed ASSET, ITY or IAL RESOURCE is agreed, then a reallocation mechanism (not shown) of financial negotiation module 49 moves the ASSET, LIABILITY or FINANCIAL RESOURCE into an UNDECIDED pool; the reallocated ASSET, LIABILITY or FINANCIAL RESOURCE is then displayed accordingly on a financial negotiation page (see figure 7). If synced and both individuals agree on the values of all ASSETS, LIABILITIES and IAL RESOURCES, then there will be no items in dispute (viz. classified as Value To Be Agreed) and the totals of each ofthe ASSETS, LIABILITIES and FINANCIAL -29— RESOURCES —as yed to each dual on the financial negotiation page—will agree. In the present embodiment, this stage is indicated by displaying a single total forthe ASSETS, a single total for LIABILITIES, and a single total for FINANCIAL RESOURCES (ratherthan te totals for each individual) on the financial negotiation page.

If synced, and there are ASSETS, LIABILITIES or FINANCIAL RESOURCES with values not agreed, then there will be different totals for Individuals 1 and 2. For each user session, the total ASSETS, LIABILITIES and FINANCIAL RESOURCES will be those stated for that user. Hence, alter onisation, system 10 displays matching financial statement pages (cf. figure 5) and financial negotiation pages (cf. figure 7) of each or all Individuals, with any disputed ASSETS, ITIES or FINANCIAL RESOURCES d. Once all values are agreed, the users will have sessions with agreeing financial statement pages.

If an ASSET, LIABILITY or FINANCIAL CE is to be deleted, a confirmation pop-up “Confirm you want to delete Y/N” is yed.

The table has two columns forthe values in the back end system — one denoting Individual 1’s valuation, and one denoting Individual 2’s valuation. The second column for Individual 2 (the other individual) is populated only once a sync operation is performed.

The “Sync Financial Statements” link or button 122 populates the ASSETS, LIABILITIES and FINANCIAL RESOURCES from the other individual alongside those ASSETS, LIABILITIES and FINANCIAL RESOURCES of Individual 1 in the back-end, and perform an update of the respective Financial Statement pages for each dual, including for those ASSETS, LIABILITIES and FINANCIAL RESOURCES where the value is not agreed (see the VALUE TO BE AGREED pool on the financial ation page, discussed below).

There is a colour legend displayed (i.e. “Red box = Not ” 124, though it should be noted that the exemplary ‘red box’ of this figure is illustrated as dashed box 126).

If sync occurs once “Financial Negotiation” has commenced, any previously agreed ASSETS, LIABILITIES and FINANCIAL RESOURCES whose value has changed are -30— moved by the reallocation mechanism back into the UNDECIDED pool (discussed below).

Financial Negotiation Figure 7 is a schematic view 140 of the page generated by financial negotiation module 49 of application 16. This module allows individuals to negotiate a split of the joint financial portfolio comprising assets, liabilities and financial resources. Financial negotiation module 49 implements a drag and drop paradigm to allocate assets between individuals, to split assets, liabilities and financial resources between individuals, and allows individuals to send proposals between each other.

Financial negotiation module 49 also handles assets, liabilities or financial resources whose values are not yet agreed (e.g. awaiting third-party valuation), and is designed to allow individuals to ue to negotiate the allocation of ASSETS, LIABILITIES and FINANCIAL RESOURCES even if the ial position (valuation) is not finalised.

That is, even though subsequent negotiation steps may require one or more s of the financial negotiation or financial valuation (part of the Financial Statement page), at least some of those steps may proceed even though the ion of ASSETS, LIABILITIES and FINANCIAL CES (also financial negotiation but not involving the allocation of ASSETS, LIABILITIES and FINANCIAL RESOURCES to individuals) is lete. This prevents complete ‘roadblocks’ arising from lack of agreement on such matters, and so accelerates the process of ent. As duals can use this onality from their laptops or other devices from home, for example, formal mediation facilities and associated costs may be avoided. In this embodiment, this module must be purchased to be used.

When assets/Iiabilities/resources are split in financial ation module 49, the values are transferred directly into the relevant individuals’ pools and, if a split asset/Iiability/resource is deleted, the aggregate asset/Iiability/resource value appears back in the “to be decided” pool and the split assetfliability/resource items are removed from the dual Participant’s pools.

Business Requirements / Rules Financial negotiation module 49 supports plural ns, as there are plural individuals (in this example, two individuals), and stores or flags each ASSET, ITY or FINANCIAL RESOURCE as belonging to one of four pools in part or in 2016/051292 -31— total. These pools are termed, in this ment, MINE 61a, THEIRS 61b, DED 61c (to which all assets, liabilities and resources are typically initially allocated), and VALUE TO BE AGREED 61d. It will be appreciated that, in embodiments in which there are more than two users/individuals, there will be a plurality of THEIRS pools corresponding to the plurality of other users.

Only when all Individuals input their agreement that an ASSET, LIABILITY or IAL CE sits with the riate individual (as agreed portions if relevant, as there are ASSETS, such as superannuation, that may need to be split so may not be allocated in their entirety) does the reallocation mechanism of financial negotiation module 49 move that item from the UNDECIDED pool 610 to the appropriate pool.

If an ASSET, LIABILITY or FINANCIAL RESOURCE is ted to different Individuals, it remains in the UNDECIDED pool 610 but is displayed in a red box (e.g. box 142, depicted with dashed lines). If the ASSET, LIABILITY or FINANCIAL RESOURCE has not been allocated to all Individuals (and hence sits as UNDECIDED by one or both Individuals), financial negotiation module 49 retains the ASSET, LIABILITY or FINANCIAL RESOURCE in that pool and does not colour it with a red box. ial negotiation module 49 employs a sync mechanism 144 or secure messaging 145. Financial negotiation module 49 provides links 146 for the duals to send proposals to the other individual/party.

The recipient of a proposal can ACCEPT, REJECT or make a COUNTER- PROPOSAL. The proposal looks like the ial negotiation page 140 and includes the pie chart ying the share of net assets with the proposed change highlighted.

The four pools can comprise ASSETS, LIABILITIES and FINANCIAL RESOURCES (denoted as positive, negative and positive values respectively). As discussed above, all ASSETS, LIABILITIES and FINANCIAL RESOURCES from the financial statement are typically initially in the UNDECIDED pool 610 (with, optionally, a scroll barfor any or all of the four pools if the associated list of ASSETS, LIABILITIES and FINANCIAL RESOURCES is long, such as being too long to display conveniently). -32— The user can swipe each ASSET, LIABILITY or FINANCIAL RESOURCE to their pool or another orthe other Individual’s pool; ASSETS can be moved ndently of LIABILITIES and FINANCIAL RESOURCES. The user can swipe an ASSET, LIABILITY or FINANCIAL RESOURCE back from the MINE or THEIRS pool 61a, 61b to r pool (e.g. to the other individuals pool or back to the UNDECIDED pool 610 but not to the VALUE TO BE AGREED pool 61d).

ASSETS, LIABILITIES or IAL CES in the VALUE TO BE AGREED pool cannot be moved to any of the other pools; these are highlighted in red (e.g. by red box 147, ed with dashed lines) on the financial negotiation page 140.

Financial negotiation module 49 displays a pie chart 148 with % labels denoting the relative split between Individuals 1 and 2. Financial negotiation module 49 updates pie chart 148 each time an asset is moved to the MINE or THEIRS pools 61a, 61b, or from either ofthose pools to the UNDECIDED pool 61c.

Financial negotiation module 49 determines and displays a total dollar value $x, $y, $2, $v for each ofthe four pools MINE 61a, UNDECIDED 61c, THEIRS 61 b and TO BE AGREE 61d respectively. Financial negotiation module 49 updates these totals each time an ASSET, LIABILITY or FINANCIAL CE is moved to the MINE or THEIRS pools 61a, 61 b, or from either of those pools to the UNDECIDED pool 61c. ial negotiation module 49 includes a mechanism, activated—for example—via a right click option or with a split button 128, to split a selected or highlighted ASSET (e.g. cash or superannuation), LIABILITY or IAL RESOURCE into two (or optionally more) items. In response to the activation of this split ism, financial negotiation module 49 displays a pop-up that allows a dollar value to be entered by each Individual. The amount must be fully split so there is no leftover amount.

Splitting an ASSET, LIABILITY or FINANCIAL CE prompts financial negotiation module 49 to generate a further item on the financial negotiation page with an incrementing number (e.g. Superannuation Individual 1, when split into two, may become Super1 Individual 1 and Super1 Individual 2) that can be moved mutually independently between the pools.

In the synced case, financial negotiation module 49 displays—in the example of two Individuals—two pie charts and two sets of totals, as described above, the first located -33— under the MINE pool and denoting the percentage and dollar split from Individual 1’s perspective, and the second located under the THEIRS pool and denoting the percentage and dollar split from dual 2‘s perspective. This is saved in the tive sessions with snapshots n to a central server 76. Once a “sync financial negotiation” has occurred and if less than predefined threshold (e.g. 20%) of the value remains to be agreed, financial negotiation module 49 displays a pop-up message stating “you are both close to finalising and preserving your future wealth by using ‘My Separation’... keep going!”.

Child Negotiation s 8A and 88 present a schematic view 150 of a page generated by child negotiation module 50 of application 16. Child negotiation module 50 allows the plurality of individuals to negotiate access to or custody of children and/or pets over a rolling window of up to two years. Child negotiation module 50 implements a method of ing days by toggling each date between the individuals. Individuals can send proposals between themselves. Holding the mouse click and dragging the mouse allows the userto select a range ofdays. Individuals can again use this functionality from their laptops or other devices from home. In this embodiment, child negotiation module 50 must be purchased to be used.

Figure 8C is a schematic view 154 of the page generated by the child negotiation module 50 of system 30 according to another embodiment ofthe present invention.

Business Requirements / Rules Child negotiation module 50 displays a grid of check boxes and/or a drop-down menu fying the most common access g structures, including (for example): 0 50-50 alternating - weekly 0 50-50 alternating - fortnightly o iday for Week 1, Thursday-Monday for Week 2 g every 2 weeks 0 etc.

Selecting one or more of these options prompts child negotiation module 50 to te the calendar accordingly as a starting point to any further negotiation or refinement (if required).

Child negotiation module 50 also displays—in the ative embodiment of figure SC—a grid of days (n x 7 days) that a user can use to select the nights that they want a given dependent. Selecting boxes in this grid prompts child negotiation module 50 to populate the calendar accordingly as a ng point to any further negotiation or refinement (if required). te children/pets appear as separate tabs in child negotiation module 50, with names pre-populated from profile module 40.

Individuals are flagged as MOTHER, FATHER, which drives the corresponding flagging of Father’s Day or Mother’s Day in the calendar as a default but can be over- ridden manually (as can all day allocations).

Individual names are pre-populated from the PROFILE page. Individual type is selected with a drop down list (including MOTHER, FATHER, GRANDFATHER, OTHER, GUARDIAN , and GUARDIAN FATHER). It is possible for both individuals to be MOTHERs or FATHERs.

Child negotiation module 50 displays a calendar, whose default view is monthly and based on Year 1 and Year 2 (as holiday tions may differ yearto year but alternate). i.e. Year1 Jan, Year1 Feb... Year2 Dec.

When the check boxes referred to above are d, child negotiation module 50 highlights the corresponding dates in the calendar, with each individual’s time highlighted in different colours for MINE and THEIRS and UNDECIDED. A colour legend (not shown) is displayed (such as MINE = light green, THEIRS = light blue, UNDECIDED = light grey).

Birthdays and Father’s Day/ Mother’s Day should, according to this embodiment, be populated in the e page if child negotiation module 50 is to be used. The module displays a message to the user asking him or her to insert his or her respective birthday so that this ation can be used by child negotiation module 50, ifthat module has been purchased and is in use.

If both individuals are MOTHERs or FATHERs, child negotiation module 50 initially allocates Individual 1 the relevant celebration day and Individual 2 the relevant other 2016/051292 -35— celebration day; these allocations can be overridden manually by the users—as they can for any of the days in the negotiation period.

The ‘sync calendars’ bring the two proposed calendars together to determine the extent of agreement. The page displays agreed days and days UNDECIDED. This relies on the sync mechanism and othen/vise negotiation is done via secure messaging. ise, either dual can send proposal scenarios where the page can be sent to the other individual for ance/rejection/counter—proposal.

By clicking on an individual day on the calendar, the colour (and associated time allocation) MUST cycle through MINE, THEIRS, UNDECIDED. This allows the individual to change the allocation of any day (including overriding previous allocations). It is possible to email a pdf file orthe like of the agreed schedule. The print out is in colour and ts the colours on-screen (viz. FATHER (blue), MOTHER (green), UNDECIDED (grey)).

A user can control application 16 database management system 62 to save a snapshot of the calendar on the website into matter database 60 and to timestamp it appropriately for that individual’s records; if this saving is done at least once, the user will be provided with a drop down list of previously-saved snapshots. The user can control application 16 to load a previous snapshot for use by application 16 as the current agreement.

Child negotiation module 50 displays a pie chart 152 with % labels denoting the ve split between Individuals 1 and 2, and updates the pie chart each time a check box is checked or cked, or if a day is checked on un-checked on the calendar.

Once a “sync calendars” has occurred and if less than 20% of the days to agree, child negotiation module 50 displays a pop up message stating “you are both close to finalising and saving your hard earned wealth by using ‘My Separation’... keep ”.

Child negotiation module 50 ys a button (“Transfer Calendar”) to allow the agreed access scheme to be input as calendar invites in a mailer (such as 'VI or Microsoft OutlookTM). Child negotiation module 50 displays links forthe individual to send proposals to the other individual. -36— The ent ofa proposal can ACCEPT, REJECT or make a COUNTER- PROPOSAL. The proposal looks like the child negotiation page and es the pie chart displaying the share of time along with the differences highlighted.

In a particular entation, each page in child negotiation module 50 represents a view forthat dependent and Participant. When the Participant is changed, the ‘Common School Term Patterns’ and the ‘Fortnightly School Term Grid’ default to the ions for that Participant but the Calendar contains time allocations for all ipants. The ‘Fortnightly School Term Grid’ differentiates time allocations by both colour and allocation description. The same colour is used consistently with other modules e.g. Financial Negotiation assets for a given Participant.

The ‘Fortnightly School Term Grid’ does not permit time allocations for the same day to overlap. Time allocations on the same day MUST be available to one or more Participants, but this is updated manually by the Participant directly into the ar.

Child negotiation module 50 may be accessed from the top menu only if the participant has purchased access to the module 50 or has an active subscription.

When a participant accesses child negotiation module 50, the application MUST populate the module with the dependents defined in Profile Module 40. System 30 creates one tab for each dependent (child, pet or ise) entered in the Profile Module 40. System 30 defaults to the first dependent on the left-most tab. On the top of each tab, there is a check box (default checked) labelled “same custody for each dependent”. Any changes to the custody le MUST be copied / ated to all other dependents only where this checkbox is selected on the tab forthat dependent.

If a Participant un-checks this check box for a given dependent and later decides to re- check this check box, then any changes to the linked custody ements will then start to be reflected on the given Dependent’s tab again.

Custody is defined as follows. Each Participant in the Custody Negotiations is allocated by system 30 with exclusive time with the respective dependents subject to there being no overlapping time allocation. The Participant defaults to the user of system 30, but there is a drop-down list to allocate custody time to other Participants to accelerate the negotiation. The Participant and Participant Type is a complete list of participants from Profile Module 40. The Participant Type is not editable and denotes 2016/051292 -37— the relationship to the dependent (i.e. Father, Mother, Grandmother, Grandfather, Uncle, Aunt, Friend). There are three ways for a Participant to enter custody details: Using a drop down menu of common “School Term Time Patterns”; Using a grid such as of2 X 7 days, to define a repeating cycle for a “Fortnightly School Term Grid“; and Using the displayed calendar ly.

All of these sections on the page are collapsible, with a +/— symbol to expand or to contract each section one at a time with section one expanded by default if no other section is ted. The drop down menu is not hidden. The label forthe drop down is “Common School Term Patterns”.

The label forthe grid is “Fortnightly School Term Grid”, while the label for the calendar is “Calendar”. The drop down menu is populated with common ns, such as 5 nights a fortnight, 2 nights a week, etc. If a Participant chooses an option from the “Common School Term Patterns” drop-down, the system populates the calendar with those common patterns: ID Description Every 9 am Saturday week 1 to 6 pm Sunday week 1, 9 am Saturday week weekend 2 to 6 pm Sunday week 2 Every 2nd 9 am Saturday week 1 to 6 pm Sunday week 1 weekend night 3 pm (after school) Thurs week 1 to 8 am (start of school) Tues week fortnight 2 4 night 3 pm (after school) Mon week 1 to 8 am (start of school) Tues week fortnight 1, 3 pm (after ) Fri week 1 to 8 am (start of ) Mon week 2 Week on week 3 pm (after school) Mon week 1 to 8 am (start of school) Mon week 2 Everything The remaining custody time for that dependent else Child negotiation module 50 fills the calendar and always displays it from the point of view of the Participant using the . Where one Participant selects another ipant for a custody allocation, a complimentary Pattern ID is selected. Similarly, where subsequent Participants directly negotiate custody for dependents, only -38— Patterns IDs not yet selected (and complementary to ng custody allocations) can be available for selection from the “Common School Term Patterns” drop-down. If the Participant uses the drop-down menu, custody type for each day is set to TERM_T|ME.

If the Participant uses the 2 x 7 day grid (2nd section), system 30 allows the Participant to click on any cell. System 30 presents collapsible help text to the Participant to indicate a cell can be clicked on to provide hour by hour composition for that day. If a cell is clicked, system 30 display a pop-up that allows the Participant to choose a Participant from a list of all Participants. lfanother ipant is selected, the grid indicates that one or multiple participants have access to the dependent on that day using coloured blocks (one per Participant) with the Name of the Participant ated from the Profile page) in each block; this means that, for split days, there may be more than one Participant block in a given box of the fortnightly grid. If additional Participants are ed from the drop down at the top of the page, system 30 automatically creates an additional row for the onal ipant. lfthere are n Participants, the grid could have n x 2 rows because the grid has two rows per Participant. If the 2nd section is used, the 1st section must collapse and no values will be active from the drop down list in the 1st section. System 30 allows Participants to select individual blocks in the grid and delete them. If a Participant chooses to delete a block prior to saving, they can do so but system 30 responds by displaying a confirmation box. Once saved, If a Participant wants to delete a block from the grid, system 30 sends a message to all Participants who have blocks on the grid informing of this deletion.

Each time a cell is tagged against a given Participant, system 30 tes the calendar accordingly, s the calendar with a colour associated with the given Participant, and updates the pie chart ing the split of y. System 30 applies all changes made to the calendar from the 1st and 2nd section two years out from the system date. System 30 displays a roll-fon/vard button once the user navigates past two years from the current system date. System 30 rolls fon/vard the same agreed patterns for a further two years.

If the Participant uses the 2 X 7 day grid, system 30 sets custody type for each day to TERM_T|ME. -39— So that the Participant can uses the calendar (3rd section) to enter custody details, the calendar can display Day, Week and Month. In either mode, system 30 presents collapsible help text to the Participant to indicate a range of custody time that can be selected for grouping as a custody type eg. term holidays.

To enter custody details in Day Mode, a ipant clicks on the day (displaying hours as horizontal bands), clicks a start time, and drags the cursorto the end time then k to create a block of time. This s a period of hours in a given day. lfthe Participant wants to drag to a subsequent day, he or she drags past midnight and system 30 responds by automatically advancing to the next day. The calendar header shows the day in the month change once the user drags the block of time past midnight for the original day in the month.

Once a Participant has selected a period (in Day, Week or Month Mode) from the ar, system 30 displays a pop-that es the start date, start time, end date and end time pre-populated for confirmation. System 30 also asks the Participant to tag this custody period against a Participant (drop down list), to select a custody type (TERM_T|ME, SCHOOL HOLIDAY, SPECIAL_DAY etc), and WHERE custody type is SPECIAL_DAY the ipant must enter a label (e.g. music lesson, father’s day, birthday, Chinese New Year, etc.).

The calendar section displays only one month at a time, but the Participant can scroll to the left or right to view arrangements in adjoining months.

The ‘Common School Term Patterns’ and the ‘Fortnightly School Term Grid’ populate the relevant week or fortnight, etc, for two years from the date of negotiation. Once a pattern is selected from the ‘Common School Term Patterns’, system 30 removes previous patterns while retaining ad-hoc time allocations.

Produce Orders Figure 9 is a schematic view 160 of the page generated by produce orders manager 45. This module allows individuals to generate draft t orders for settlement by their solicitor or barrister, and subsequent submission to the Court. Produce orders manager 45 presents a list of supplementary questions that are ed to populate the nt sections ofthe draft orders, in addition to the outputs of financial negotiation module 49 and/or child negotiation module 50, and information from e module 40 and financial statement module 47.

Produce orders manager 45 includes (or accesses, such as from ordertemplates and rules database 66) a range of templates to cater forjurisdictional variations, and the supplementary questions will also depend on the relevantjurisdiction. Produce orders manager 45, in this ment, must be purchased to be used.

Business Requirements / Rules Produce orders manager 45 displays the following questions requiring responses in a table, grouped as follows: Relationship 162 - Have you completed a relationship separation course? — if N, then ask if we can send info forthis via email Is there a restraining order (e.g. an AVO) against you? If Y, then ask are you permitted to correspond electronically? If N, then no messaging or emails from system 10 will be permitted, only “session sharing” mode Children 164 - Are you seeking child support? If Y, then complete ‘Form 13’ (to which a link is provided) and enter living costs into the generated form - Have you re-partnered? If Y, then te column ‘your new partner“ in “Net Assets” and “Negotiate” - Has a family report been prepared? If Y, populate ren’s Days” accordingly. If N, do you want system 10 to recommend a recognised psychologist [i.e. with referrals engine 58] Financial 166 - Are the financial assets ted? If N, then send finalise option to both parties and prompt the user(s) to request the purchase of produce orders manager 45; iate’ page is greyed out. If Y, that is, financial assets are contested, ask “Do you have independent valuations”? If Y, mark those assets and liabilities as independently valued on the ial statement page 120 with independent valuation checkbox not shown. If N, then ask “Do you want ‘My Separation’ to end a recognised valuer?” - Funds contributed to spouse since separation? lfY, then ask “Number of payments (or other contribution)”; Number of payments = ‘x’, then Payment 1 L" to ‘x’ is listed beneath _41_ - Do you have tax returns not yet completed? If Y, how many years are outstanding? Then provide labels forthe respective years with an amount for te. “Can you arrange an estimate from your accountant on letterhead?" - Do you have a payment plan? lfY, display “Populate your liability and payment amount and frequency on financial statement page 120 - Do you have current bank statements for liabilities and certificates for asset ownership and value? (Documents not to be loaded into the site but sent accompanying the orders on the “produce ” page 160) - Do you have additional third party evidence? Please state the item and nature and te on financial statement page 120 that additional documentation to be supplied - Are you receiving ment benefits? If Y, cannot have spousal support agreement - Are you seeking spousal maintenance? If Y, then complete ‘Form 13‘ (to which a link is provided) and enter living costs into the generated form - If net financial statement is negative, ask “Is net assets on negative?” If Y, ask “Have you ered a bankruptcy claim?” Procedural 168 - Are you legally represented? Ythen provide 8 fields: Solicitor Name, Firm name, Address1, AddressZ, State, Postcode, phone number, email.

Produce orders manager 45 displays a drop down menu to select in which COUNTRY (at 170) and STATE (at 172) the orders are to be lodged. This selection drives the selection of the relevant templates. Produce orders manager 45 displays a CE ORDERS” button 174 that generates a set of orders in pdfand launches Adobe Acrobat or other pdf viewer.

Produce orders manager 45 uses information from profile page 90, the outcomes of the financial and/or child negotiation from financial ation module 49 and/or child negotiation module 50, and the answers to the questions bed above to produce consent orders using a suitable orders template. The orders templates are stored in emplates and rules database 66. As described above, the orders templates are localised to the relevant country orjurisdiction, and the orders are date and time stamped. Optionally, system 10 may interface with the relevant electronic filing system used by the given jurisdiction (eg. the Family Court Casetrack system in Australia).

The user can generate orders as many times as desired (though only for the named users, to prevent on-selling) once produce orders manager 45 has been purchased.

System 30 may also include a scripting language (referred to as an ‘orders mark-up language‘) so that elements of orders may be stored as logical components; these logical components are also stored in order templates and rules se 66 and can be individually d and ively combined by system 30 to create orders templates. This allows system 30 to te an orders template for a particular country orjurisdiction comprising a plurality ofthese logical components, using a te “agenda”, “TOC” (table of contents) or “instructions” (also stored in order tes and rules database 66) that describe what components constitute a given orders template and in what order. The individual logical components can be static text or contain mappable fields that produce orders manager 45 populates with information from the information submitted in response to prompts presented to users by produce orders manager 45 and/or from other s, when generating a set of orders. These logical components may contain code loops where instructions to populate content occurs while a given condition is or is not met. (For example, FOR each asset in the financial statement, DO populate the financial orders agreement section). Each logical component and the ultimate orders template is stamped with a country, jurisdiction, start date and end date, so that system 30 can manage orders template versions and individual orders ents dually within a given te (while leaving the rest ofa particulartemplate ged), so thatthe orders templates need not be updated in their entirely each time one ofthe logical components is updated. It should be noted that, when creating Orders, system 30 pushes an agreed snapshot ofthe negotiation (concerning dependent finances or otherwise) into the Orders to reflect a precise point of agreement between the parties.

Figures 10A and 1GB t a flow chart ofthe process implemented by financial statement module 47 of application 16. This process may also be described by the following pseudo code: ial Statement f/ Enter financial information Box: GUI / Front-end: Enter Asset, Liability or Financial Resource and associated values Box: Business Rules Engine: Add Asset, Liability or Financial Resource Box: Matter Database: Store Updated Financial Position Box: GUI / end: Delete , Liabilities or Financial Resources and associated values Box: s and Messages Engine: Retrieve “Are you sure you want to delete this asset, liability or resource?” message (question) Box: GUI / Front-end: Display confirmation question // Handle deletion of items Diamond: Front-end / GUI: IF confirm intent to delete YES: Box: Business Rule Engine: Delete asset, liability or resource Box: Matter Database: Store updated financial position Box: Front-end / GUI: Display completion message NO: End f/ Update visual representation of financials Box: Negotiation Engine: Initiate update to pie charts and financial statistics (local session) Box: Rendering Engine: Determine coordinates, colour and ters for the updated charts and statistics (local session) Box: end / GUI: Update charts and statistics (local session) // Sync session views between parties Box: Front-end / GUI: Press “Sync Financial Statements” button (or link) Diamond: Business Rules Engine: IF connected session (to at least one other individual) and the sync button (or link) pressed NO: [do nothing] // continue with standalone (local) n YES: Box: onisation Manager: Initiate synchronisation Box: Initiate update to pie charts and ial tics (remote session) Box: Rendering Engine: Determine coordinates, colour and parameters forthe updated charts and statistics (remote session) Box: Front-end / GUI: Update charts and tics (remote n) // Handle values not agreed but allows individuals to keep going and enter/delete/ edit ASSETS, LIABILITIES and /or FINANCIAL RESOURCES Box: Synchronisation Manager: Initiate synchronisation Diamond: Business Rules Engine: IF there are assets, liabilities or resources with values are NOT agreed W0 2017l117623 _44_ NO: Box: Continue // Back to the diamond testing IF the session is connected and the sync button is pressed YES: Box: Business Rules Engine: fy , liabilities or resources with values NOT agreed Box: ing Engine: ine coordinates, colour and parameters forthe highlight box Box: Front-end / GUI: Draw a red line around the disputed asset/ liability / resource and display the disputed values (remote and local) // Suggest referral Box: Prompts and Messages Engine: Retrieve “Do you need an independent valuation?” message Box: Front-end / GUI: Display valuation message Diamond: end / GUI: IF individuals want a valuer NO: Box: Continue // Back to the diamond testing if there are ASSETS / ITIES / RESOURCES with values not agreed YES: Box: Referrals Engine: te retrieval of valuers from Referrals Database Box: Referrals Database: Return valuer list (subject to one or more criteria e.g. location) Box: Prompts and Messages Engine: ve “Here are some valuers [in your area]” message template and insert list from Referrals Database (including contact details, links to websites etc.) Box: Front-end / GUI: Display valuer message // Selection of link/ referral to be handled in separate flow Box: Front-end / GUI: Continue // Back to the diamond testing if there are ASSETS / LIABILITIES / RESOURCES with values not agreed; essentially a DO WHILE loop but cannot draw easily in the flow m of figures 10A and 10B so implemented using IF Figures 11A and 11B t a flow chart ofthe process implemented by financial negotiation module 49 of application 16. This process may also be described by the following pseudo code: _45_ Financial Negotiation Process f/ ate success d: Business Rules Engine: IF all ASSETS, LIABILITIES AND FINANCIAL RESOURCES are allocated to an individual NO: Continue to next diamond YES: Box: Messages Engine: Retrieve atulations, you have completed sharing your assets and liabilities!” comment // completion message Box: Rendering Engine: ine coordinates, colour and parameters forthe message Box: Front-end / GUI: Display completion message Box: Front-end / GUI: End f/ Encourage completion Diamond: Business Rules : IF Net ASSETS >= 80% (configurable in Business Rules Engine) NO: Continue // move to negotiation (next) sub-flow where individuals allocate ASSETS or LIABILITIES YES: Box: Messages Engine: Retrieve “Keep going, you have divided over 80% of your net assets!” comment // progress message Box: Rendering Engine: Determine nates, colour and parameters forthe message Box: Front-end / GUI: Display progress message Box: Front-end / GUI: Continue // move to negotiation (next) sub-flow where individuals allocate ASSETS, LIABILITIES or FINANCIAL // Negotiate l) Box: GUI: Swipe ASSETS, LIABILITIES or FINANCIAL RESOURCES from UNDECIDED list to an individual OR swipe from one individual to the other OR split assets between duals // IF the allocation of an ASSET, LIABILITY or FINANCIAL RESOURCE is not agreed, the ASSET, LIABILITY or FINANCIAL RESOURCE will stay in the UNDECIDED pool and cannot be moved until both individuals agree — one will swipe the ASSET, TY or FINANCIAL RESOURCE to their MINE pool and the other individual must swipe the ASSET, LIABILITY or IAL RESOURCE to their THEIRS pool or vice versa; this allows negotiation to continue even if allocation of one or more ASSETS, LIABILITIES or FINANCIAL RESOURCES is not agreed WO 17623 —46— Box: Negotiation Engine: Update state of negotiation (in memory/volatile storage) Box: Matter Database: Store updated state of negotiation (write to database / persistent e) Box: Negotiation Engine: Initiate update to pie charts and negotiation statistics (local session) Box: Rendering Engine: Determine coordinates, colour and parameters for the updated charts and statistics (local session) Box: Front-end / GUI: Update charts and tics (local session) // Sync session views between parties Box: Front-end / GUI: Press sync button (or link) Diamond: Business Rules Engine: IF sync button pressed NO: Continue // back to the test IF all ASSETS, LIABILITIES and FINANCIAL RESOURCES are ted to an individual YES: Box: Synchronisation Manager: Initiate synchronisation // Handle disputed ASSET, LIABILITY or FINANCIAL RESOURCE allocations but allows individuals to keep negotiating Diamond: IF there are disputed ASSET, LIABILITY or FINANCIAL RESOURCE allocations YES: Box: Return all disputed ASSETS, LIABILITIES and FINANCIAL RESOURCES to the UNDECIDED pool Box: ine coordinates, colour and parameters forthe updated charts and tics (local and remote sessions) Box: Update charts and statistics and portfolio view (local and remote sessions) Box: Continue // back to the test IF all , LIABILITIES and FINANCIAL RESOURCES are allocated to an individual NO: Continue // to next test: IF ASSETS, LIABILITIES or FINANCIAL RESOURCES or their values have changed since the last Sync // Handle ASSETS, LIABILITIES or FINANCIAL CES that have d , deleted or changed value) Diamond: IF ASSETS, LIABILITIES or FINANCIAL RESOURCES or their values have d since the last Sync YES: Box: Return changed ASSETS, LIABILITIES and FINANCIAL RESOURCES to the UNDECIDED pool AND delete any W0 2017l117623 _47_ ASSETS, LIABILITIES or FINANCIAL RESOURCES which have been removed from the Financial ent Box: Determine nates, colour and parameters for the updated charts and statistics AND forthe portfolio view (local and remote sessions) Box: Update charts and statistics AND portfolio view (local and remote sessions) Box: Continue // back to the test IF all ASSETS, LIABILITIES and FINANCIAL RESOURCES are ted to an individual NO: Box: Negotiation Engine: Initiate update to pie charts and negotiation tics (remote n) Box: Rendering Engine: ine coordinates, colour and parameters for the updated charts and statistics (remote session) Box: Front-end / GUI: Update charts and statistics (remote Box: Front-end / GUI: Continue (remote session) // back to the test IF all ASSETS, LIABILITIES or FINANCIAL RESOURCES are ted to an individual Figures 12A and 12B present a flow chart ofthe process implemented by child negotiation module 50 of application 16. This process may also be described by the following pseudo code: Child Negotiation l/Celebrate success Diamond: Business Rules Engine: IF all days are allocated to an individual NO: Continue to next diamond YES: Box: Messages Engine: Retrieve “Congratulations, you have completed agreeing your child access!” comment // success message Box: Rendering Engine: Determine coordinates, colour and parameters forthe message Box: Front-end / GUI: Display completion message Box: Front-end / GUI: End urage completion —48— Diamond: Business Rules Engine: IF number of days agreed >= 80% (configurable in Business Rules Engine) NO: Continue YES: Box: Messages Engine: Retrieve “Keep going, you have agreed over 80% of your child access!” comment // progress message Box: Rendering Engine: Determine coordinates, colour and parameters forthe message Box: Front-end / GUI: Display message Box: end / GUI: Continue // to next sub-flow where individuals can select from pre-defined access patterns if they wish // Leverage common access patterns (to accelerate agreement and to minimise the need for repetitive selections) Diamond: Front-end / GUI: IF individual selects one of the pre-defined access patterns NO: Continue // to Negotiate sub-flow YES: Box: Negotiation Engine: Determine days to claim for the individual (local session) Box: ing Engine: Determine coordinates, colour and parameters forthe days to be d for the individual (local session) Box: Front-end / GUI: Colour relevant days on calendar ng the predefined access pattern (local session) Box: ue // to ate sub-flow // Negotiate (manual) Box: Front-end / GUI: Select days by pressing repeatedly on a given day or selecting a range of days Box: Negotiation Engine: Update state of negotiation (in memory/volatile storage) Box: Matter Database: Store updated state of ation (write to database / persistent storage) Box: Negotiation : Initiate update to pie charts and negotiation statistics (local session) Box: Rendering Engine: Determine nates, colour and parameters for the updated charts and tics (local session) Box: Front-end / GUI: Update charts and statistics (local session) Box: Front-end / GUI: Continue // Back to the diamond testing IF all days are allocated to an individual // Sync session views between parties Box: Front-end / GUI: Press sync button W0 2017l117623 Diamond: Business Rules Engine: IF sync button pressed NO: Continue // Back to the diamond testing IF all days are allocated to an individual YES: Box: Synchronisation r: Initiate synchronisation Box: Negotiation Engine: Initiate update to pie charts and negotiation statistics (remote session) Box: Rendering : Determine coordinates, colour and parameters forthe updated charts and statistics (remote session) Box: Front-end / GUI: Update charts and statistics (remote session) Box: Front-end / GUI: Continue // Back to the d testing IF all days are allocated to an individual If Handle days not agreed but allows individuals to keep going and selecting days on the ar Diamond: IF there are days NOT agreed NO: Return to start // Back to the diamond testing IF all days are allocated to an individual YES: Box: ation Engine: Set the disputed days back to “UNDECIDED” //days not agreed remain flagged / coloured as UNDECIDED Box: Rendering Engine: Set coordinates, colour and parameters forthe days to NOT AGREED to the relevant colour (e.g. GREY) Box: Front-end / GUI: Update calendar (local and remote sessions) // Suggest Referrals Box: Prompts and Messages Engine: Retrieve “Do you need a family report or advice regarding access?” Box: Front-end / GUI: Display family report message Diamond: Front-end I GUI: IF duals want a family report or advice regarding access NO: Continue YES: Box: Referrals Engine: Initiate retrieval of child experts from Referrals Database -50— Box: Referrals Database: Return Child Expert list (subject to one or more criteria e.g. location) Box: s and Messages : Retrieve “Here are some child experts [in your area]" message template and insert list from Referrals Database (including contact details, links to es etc.) Box: Front-end / GUI: y family report/ access advice message // Selection of linkf referral to be handled in separate flow Box: Front-end / GUI: Continue // Back to the diamond testing IF all days are ted to an individual; essentially a DO WHILE loop but cannot draw easily in the flow diagram of s 12A and 128 so implemented using IF] It should also be noted that system 30 may be adapted so that the amount of information need be entered for each module or engine thereof is minimized. Each module or engine presents the minimum number of questions, check boxes etc, required by a userto carry out the function ofthat module or engine. For example, produce orders manager 45 can access the information submitted by the user(s) in response to prompts presented by profile module 40, financial ent module 47, financial negotiation module 49 and child negotiation module 50, so the user does not—as far as is feasible—have to enter the same information twice. As a result, each module may be regarded as the ‘master module’ for a given piece of information that it receives from the users.

It will be understood to those persons skilled in the art ofthe invention that many modifications may be made without departing from the scope ofthe invention.

In the claims which follow and in the ing description ofthe invention, except where the context requires othen/vise due to express ge or necessary implication, the word “comprise” or variations such as “comprises” or “comprising” is used in an inclusive sense, i.e. to specify the presence of the stated features but not to -51— preclude the presence or addition of further features in various embodiments of the invention.

It will also be understood that the reference to any prior art in this specification is not, and should not be taken as an ledgement or any form of suggestion that the prior art forms part of the common general knowledge in any country. -52—

Claims (14)

1. A method for processing data sets that ee, comprising: a) receiving a plurality of data sets of corresponding elements from a respective plurality of corresponding users; b) comparing elements of corresponding elements of the data sets; c) identifying one or more corresponding ts ofthe data sets that are not in agreement across all ofthe data sets; cl) outputting the corresponding elements of the data sets that are not in 10 agreement across all of the data sets to the users; e) alerting the users to the one or more elements ofthe respective data set corresponding to the respective userthat are not in ent across all ofthe data sets; f) receiving amendment input from at least one of the users; 15 9) amending at least one of the data sets according to the amendment input; h) checking whetherthere remain any corresponding elements of the data sets that are not in agreement across all of the data sets. 20

2. A method as claimed in claim 1, wherein first and second data sets are received from first and second ponding users.

3. A method as claimed in claim 1, including repeating steps 0) to h) one or more times until there remain no corresponding elements ofthe data sets that are not in 25 agreement across all of the data sets.

4. A method as claimed in claim 1, ing at least partially further processing the corresponding elements of the data sets that agree across the data sets while continuing to resolve or awaiting resolution of disagreement between the one or more 30 corresponding ts of the data sets that are not in agreement across all of the data sets.

5. A method as claimed in claim 1, including splitting each of one or more corresponding elements of the data sets into a plurality of elements. -53—

6. A method as claimed in claim 1, wherein at least some of the elements of the data sets correspond to financial values.

7. A method as claimed in claim 1, further comprising flagging the corresponding elements of the data sets that are not in agreement across all of the data sets, or storing or flagging the corresponding elements of the data sets that are not in agreement across all of the data sets as undecided.

8. A method as claimed in claim 1, further comprising displaying the elements or data 10 indicative of the ts to the users.

9. A method as claimed in claim 1, wherein at least some of the elements of the data sets correspond to , liabilities or ial ces. 15

10. A method as claimed in claim 1, wherein at least some of the elements of the data sets correspond to dependent access.

11. A method as claimed in claim 10, comprising presenting to a user a plurality of tools configured to control a child negotiation module that is llable to negotiate 20 said dependent .

12. A method as claimed in claim 11, wherein the plurality of tools comprise one or more of (i) a drop down menu listing common dependent access patterns, (ii) a grid sing one or more weeks (such as a fortnightly grid), and (iii) a selectively 25 viewable full calendar.

13. A method as claimed in claim 1, further comprising displaying the elements or data indicative of the elements to the users d or flagged into a ity of pools of elements.

14. A method as claimed in claim 13, wherein the elements of the data sets correspond to assets, liabilities or financial resources of the users and the pools of elements include pools corresponding to the respective assets, liabilities or financial resources of the respective users. WO 17623 _54